December 2017 - mice-discuss - lists.micemn.net

Re: Attribute Length Error today

by Darin Steffl

It's possible it was sending default earlier and our consultant fixed it when he logged in between 1:27pm and 1:45pm. If someone wants to verify, that'd be great. On Fri, Dec 8, 2017 at 5:48 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > I do not know much about how Mikrotik works. I agree that the filters do > not look like you are sending default, I was just seeing it from Andy's > post. > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] *On Behalf > Of *Darin Steffl > *Sent:* Friday, December 08, 2017 5:39 PM > > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] Attribute Length Error today > > > > Looking at route filters right now and that I attached, I don't see that > I'm advertising a default route unless I'm looking in the wrong spot. I did > not setup any portion of the BGP as I know I'm not an expert or comfortable > setting it up, thus why I hired a consultant to do it for me. They're a big > Mikrotik consultant from Missouri. > > > > I only see us advertising 204.73.77.0/24, 162.255.252.0/22 in our route > filters right now that I sent. > > > > > > > > On Fri, Dec 8, 2017 at 5:29 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > > In looking at it, do you happen to know why you were sending a default > route? Has that been corrected? > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] *On Behalf > Of *Darin Steffl > *Sent:* Friday, December 08, 2017 5:16 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] Attribute Length Error today > > > > Hey all, > > > > I sent the following to my Mikrotik consultant who set this up for me and > his response is below. Anyone familiar with Mikrotik that knows the easy > way to do this? We have MICE filters setup but not sure the correct way to > do this without messing anything up further. He had the route filters out > of order in our Mikrotik which is why I wasn't seeing MICE traffic. Once he > fixed that, we're now receiving 500+ mbps from MICE and its stable on our > end. But if we're still sending incorrect route announcements, I want to > fix that so I don't cause issues. I found two related forum posts on how to > change this in my router but I have a couple MICE filters as shown in the > attachment. Thanks > > > > My cell is 507-261-7690 <(507)%20261-7690> > > > > > > My email to consultant: > > Under the technical page of their website http://micemn.net/technical.html > I see the following note "Note that your BGP sessions to the route servers > likely need no bgp enforce-first-as or similar. The route servers do not > add the MICE AS to the AS path." A quick search of Mikrotik forums shows > that the equivalent to this setting is to "set-bgp-prepend=0" for the MICE > peer. I'm not sure of this so want clarification to see if we need to make > this change in order for traffic to start going through MICE. > > https://forum.mikrotik.com/viewtopic.php?t=55798 > > https://forum.mikrotik.com/viewtopic.php?t=43498 > > > > > > Consultant response: > > Your MICE connection should have had traffic assuming that you were > advertising your prefixes to them. Their BGP session should not add their > AS, so that should not matter. You should not need to change that, I would > have to look to see why you are not seeing traffic. > > > > > > On Fri, Dec 8, 2017 at 4:55 PM, Andy Koch <akoch(a)wiscnet.net> wrote: > > On 08 December 2017 at 16:15:59, Justin Krejci wrote: > > Yup > > > > > > Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor > 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200 > > Dec 8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF > FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE > 6CFF 5918 CC49 4D16 A2FF E8 > > > >From this UPDATE dump, this parser helps quite a bit to decode what is > going on: http://bgpaste.convergence.cx/ > > Looks like the AS_PATH was 0 bytes long, which is invalid and Frank's > router did the only thing it knows to do on BGP errors - drop the session. > > Further from the decode: > The NEXT_HOP was 206.108.255.89 > And the Routes were 204.73.77.0/24, 162.255.252.0/22 and 0.0.0.0/0 > > Looks like Minnesota WiFi should check on their route announcements. > > HTH, > Andy > > > > > > -- > > Darin Steffl > > Minnesota WiFi > > www.mnwifi.com > > 507-634-WiFi > > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > > > -- > > Darin Steffl > > Minnesota WiFi > > www.mnwifi.com > > 507-634-WiFi > > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 8, 2017

Re: Attribute Length Error today

by Jeremy Lumby

I do not know much about how Mikrotik works. I agree that the filters do not look like you are sending default, I was just seeing it from Andy's post. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Darin Steffl Sent: Friday, December 08, 2017 5:39 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Attribute Length Error today Looking at route filters right now and that I attached, I don't see that I'm advertising a default route unless I'm looking in the wrong spot. I did not setup any portion of the BGP as I know I'm not an expert or comfortable setting it up, thus why I hired a consultant to do it for me. They're a big Mikrotik consultant from Missouri. I only see us advertising 204.73.77.0/24, 162.255.252.0/22 in our route filters right now that I sent. On Fri, Dec 8, 2017 at 5:29 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: In looking at it, do you happen to know why you were sending a default route? Has that been corrected? From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Darin Steffl Sent: Friday, December 08, 2017 5:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Attribute Length Error today Hey all, I sent the following to my Mikrotik consultant who set this up for me and his response is below. Anyone familiar with Mikrotik that knows the easy way to do this? We have MICE filters setup but not sure the correct way to do this without messing anything up further. He had the route filters out of order in our Mikrotik which is why I wasn't seeing MICE traffic. Once he fixed that, we're now receiving 500+ mbps from MICE and its stable on our end. But if we're still sending incorrect route announcements, I want to fix that so I don't cause issues. I found two related forum posts on how to change this in my router but I have a couple MICE filters as shown in the attachment. Thanks My cell is 507-261-7690 My email to consultant: Under the technical page of their website http://micemn.net/technical.html I see the following note "Note that your BGP sessions to the route servers likely need no bgp enforce-first-as or similar. The route servers do not add the MICE AS to the AS path." A quick search of Mikrotik forums shows that the equivalent to this setting is to "set-bgp-prepend=0" for the MICE peer. I'm not sure of this so want clarification to see if we need to make this change in order for traffic to start going through MICE. https://forum.mikrotik.com/viewtopic.php?t=55798 https://forum.mikrotik.com/viewtopic.php?t=43498 Consultant response: Your MICE connection should have had traffic assuming that you were advertising your prefixes to them. Their BGP session should not add their AS, so that should not matter. You should not need to change that, I would have to look to see why you are not seeing traffic. On Fri, Dec 8, 2017 at 4:55 PM, Andy Koch <akoch(a)wiscnet.net> wrote: On 08 December 2017 at 16:15:59, Justin Krejci wrote: > Yup > > > Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200 > Dec 8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE 6CFF 5918 CC49 4D16 A2FF E8 >From this UPDATE dump, this parser helps quite a bit to decode what is going on: http://bgpaste.convergence.cx/ Looks like the AS_PATH was 0 bytes long, which is invalid and Frank's router did the only thing it knows to do on BGP errors - drop the session. Further from the decode: The NEXT_HOP was 206.108.255.89 And the Routes were 204.73.77.0/24, 162.255.252.0/22 and 0.0.0.0/0 Looks like Minnesota WiFi should check on their route announcements. HTH, Andy -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi Like us on Facebook To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi Like us on Facebook To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 8, 2017

Re: Attribute Length Error today

by Darin Steffl

Looking at route filters right now and that I attached, I don't see that I'm advertising a default route unless I'm looking in the wrong spot. I did not setup any portion of the BGP as I know I'm not an expert or comfortable setting it up, thus why I hired a consultant to do it for me. They're a big Mikrotik consultant from Missouri. I only see us advertising 204.73.77.0/24, 162.255.252.0/22 in our route filters right now that I sent. On Fri, Dec 8, 2017 at 5:29 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > In looking at it, do you happen to know why you were sending a default > route? Has that been corrected? > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] *On Behalf > Of *Darin Steffl > *Sent:* Friday, December 08, 2017 5:16 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] Attribute Length Error today > > > > Hey all, > > > > I sent the following to my Mikrotik consultant who set this up for me and > his response is below. Anyone familiar with Mikrotik that knows the easy > way to do this? We have MICE filters setup but not sure the correct way to > do this without messing anything up further. He had the route filters out > of order in our Mikrotik which is why I wasn't seeing MICE traffic. Once he > fixed that, we're now receiving 500+ mbps from MICE and its stable on our > end. But if we're still sending incorrect route announcements, I want to > fix that so I don't cause issues. I found two related forum posts on how to > change this in my router but I have a couple MICE filters as shown in the > attachment. Thanks > > > > My cell is 507-261-7690 <(507)%20261-7690> > > > > > > My email to consultant: > > Under the technical page of their website http://micemn.net/technical.html > I see the following note "Note that your BGP sessions to the route servers > likely need no bgp enforce-first-as or similar. The route servers do not > add the MICE AS to the AS path." A quick search of Mikrotik forums shows > that the equivalent to this setting is to "set-bgp-prepend=0" for the MICE > peer. I'm not sure of this so want clarification to see if we need to make > this change in order for traffic to start going through MICE. > > https://forum.mikrotik.com/viewtopic.php?t=55798 > > https://forum.mikrotik.com/viewtopic.php?t=43498 > > > > > > Consultant response: > > Your MICE connection should have had traffic assuming that you were > advertising your prefixes to them. Their BGP session should not add their > AS, so that should not matter. You should not need to change that, I would > have to look to see why you are not seeing traffic. > > > > > > On Fri, Dec 8, 2017 at 4:55 PM, Andy Koch <akoch(a)wiscnet.net> wrote: > > On 08 December 2017 at 16:15:59, Justin Krejci wrote: > > Yup > > > > > > Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor > 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200 > > Dec 8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF > FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE > 6CFF 5918 CC49 4D16 A2FF E8 > > > >From this UPDATE dump, this parser helps quite a bit to decode what is > going on: http://bgpaste.convergence.cx/ > > Looks like the AS_PATH was 0 bytes long, which is invalid and Frank's > router did the only thing it knows to do on BGP errors - drop the session. > > Further from the decode: > The NEXT_HOP was 206.108.255.89 > And the Routes were 204.73.77.0/24, 162.255.252.0/22 and 0.0.0.0/0 > > Looks like Minnesota WiFi should check on their route announcements. > > HTH, > Andy > > > > > > -- > > Darin Steffl > > Minnesota WiFi > > www.mnwifi.com > > 507-634-WiFi > > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 8, 2017

Re: Attribute Length Error today

by Jeremy Lumby

In looking at it, do you happen to know why you were sending a default route? Has that been corrected? From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Darin Steffl Sent: Friday, December 08, 2017 5:16 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Attribute Length Error today Hey all, I sent the following to my Mikrotik consultant who set this up for me and his response is below. Anyone familiar with Mikrotik that knows the easy way to do this? We have MICE filters setup but not sure the correct way to do this without messing anything up further. He had the route filters out of order in our Mikrotik which is why I wasn't seeing MICE traffic. Once he fixed that, we're now receiving 500+ mbps from MICE and its stable on our end. But if we're still sending incorrect route announcements, I want to fix that so I don't cause issues. I found two related forum posts on how to change this in my router but I have a couple MICE filters as shown in the attachment. Thanks My cell is 507-261-7690 My email to consultant: Under the technical page of their website http://micemn.net/technical.html I see the following note "Note that your BGP sessions to the route servers likely need no bgp enforce-first-as or similar. The route servers do not add the MICE AS to the AS path." A quick search of Mikrotik forums shows that the equivalent to this setting is to "set-bgp-prepend=0" for the MICE peer. I'm not sure of this so want clarification to see if we need to make this change in order for traffic to start going through MICE. https://forum.mikrotik.com/viewtopic.php?t=55798 https://forum.mikrotik.com/viewtopic.php?t=43498 Consultant response: Your MICE connection should have had traffic assuming that you were advertising your prefixes to them. Their BGP session should not add their AS, so that should not matter. You should not need to change that, I would have to look to see why you are not seeing traffic. On Fri, Dec 8, 2017 at 4:55 PM, Andy Koch <akoch(a)wiscnet.net> wrote: On 08 December 2017 at 16:15:59, Justin Krejci wrote: > Yup > > > Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200 > Dec 8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE 6CFF 5918 CC49 4D16 A2FF E8 >From this UPDATE dump, this parser helps quite a bit to decode what is going on: http://bgpaste.convergence.cx/ Looks like the AS_PATH was 0 bytes long, which is invalid and Frank's router did the only thing it knows to do on BGP errors - drop the session. Further from the decode: The NEXT_HOP was 206.108.255.89 And the Routes were 204.73.77.0/24, 162.255.252.0/22 and 0.0.0.0/0 Looks like Minnesota WiFi should check on their route announcements. HTH, Andy -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi Like us on Facebook To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 8, 2017

Re: Attribute Length Error today

by Darin Steffl

Hey all, I sent the following to my Mikrotik consultant who set this up for me and his response is below. Anyone familiar with Mikrotik that knows the easy way to do this? We have MICE filters setup but not sure the correct way to do this without messing anything up further. He had the route filters out of order in our Mikrotik which is why I wasn't seeing MICE traffic. Once he fixed that, we're now receiving 500+ mbps from MICE and its stable on our end. But if we're still sending incorrect route announcements, I want to fix that so I don't cause issues. I found two related forum posts on how to change this in my router but I have a couple MICE filters as shown in the attachment. Thanks My cell is 507-261-7690 <(507)%20261-7690> My email to consultant: Under the technical page of their website http://micemn.net/technical.html I see the following note "Note that your BGP sessions to the route servers likely need no bgp enforce-first-as or similar. The route servers do not add the MICE AS to the AS path." A quick search of Mikrotik forums shows that the equivalent to this setting is to "set-bgp-prepend=0" for the MICE peer. I'm not sure of this so want clarification to see if we need to make this change in order for traffic to start going through MICE. https://forum.mikrotik.com/viewtopic.php?t=55798 https://forum.mikrotik.com/viewtopic.php?t=43498 Consultant response: Your MICE connection should have had traffic assuming that you were advertising your prefixes to them. Their BGP session should not add their AS, so that should not matter. You should not need to change that, I would have to look to see why you are not seeing traffic. On Fri, Dec 8, 2017 at 4:55 PM, Andy Koch <akoch(a)wiscnet.net> wrote: > On 08 December 2017 at 16:15:59, Justin Krejci wrote: > > Yup > > > > > > Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor > 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200 > > Dec 8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF > FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE > 6CFF 5918 CC49 4D16 A2FF E8 > > > >From this UPDATE dump, this parser helps quite a bit to decode what is > going on: http://bgpaste.convergence.cx/ > > Looks like the AS_PATH was 0 bytes long, which is invalid and Frank's > router did the only thing it knows to do on BGP errors - drop the session. > > Further from the decode: > The NEXT_HOP was 206.108.255.89 > And the Routes were 204.73.77.0/24, 162.255.252.0/22 and 0.0.0.0/0 > > Looks like Minnesota WiFi should check on their route announcements. > > HTH, > Andy > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 8, 2017

Re: Attribute Length Error today

by Andy Koch

On 08 December 2017 at 16:15:59, Justin Krejci wrote: > Yup > > > Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200 > Dec 8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE 6CFF 5918 CC49 4D16 A2FF E8 >From this UPDATE dump, this parser helps quite a bit to decode what is going on: http://bgpaste.convergence.cx/ Looks like the AS_PATH was 0 bytes long, which is invalid and Frank's router did the only thing it knows to do on BGP errors - drop the session. Further from the decode: The NEXT_HOP was 206.108.255.89 And the Routes were 204.73.77.0/24, 162.255.252.0/22 and 0.0.0.0/0 Looks like Minnesota WiFi should check on their route announcements. HTH, Andy

Dec. 8, 2017

Re: Attribute Length Error today

by Justin Krejci

Yup Dec 8 13:41:40.262 CST: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.1 3/11 (invalid or corrupt AS path) 3 bytes 400200 Dec 8 13:41:40.262 CST: BGP: 206.108.255.1 Bad attributes FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 0E40 0101 0040 0200 4003 04CE 6CFF 5918 CC49 4D16 A2FF E8 ________________________________________ From: MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] on behalf of Frank Bulk [fbulk(a)MYPREMIERONLINE.COM] Sent: Friday, December 08, 2017 4:10 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Attribute Length Error today Anyone else see this today with both MICE route reflectors? Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) Dec 8 13:44:36 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Dec 8 13:45:23 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Frank

Dec. 8, 2017

Re: Attribute Length Error today

by Doug McIntyre

On Fri, Dec 08, 2017 at 10:10:00PM +0000, Frank Bulk wrote: >Anyone else see this today with both MICE route reflectors? > >Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) >Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) >Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) >Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) >Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) >Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) >Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) >Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) >Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) >Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) >Dec 8 13:44:36 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) >Dec 8 13:45:23 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Which AS are you? No, but at the same time on the BIRD side we saw 2017-12-08 13:39:55 <RMT> NASN_26794: Received: Invalid attribute length: 400200400304ce6c 2017-12-08 13:39:55 <RMT> NASN_54578: Received: Invalid attribute length: 400200400304ce6c 2017-12-08 13:39:55 <RMT> NASN_32609: Received: Malformed AS_PATH: 400200 2017-12-08 13:39:55 <RMT> NASN_22402: Received: Invalid attribute length: 400200400304ce6c 2017-12-08 13:39:55 <RMT> NASN_16842: Received: Malformed AS_PATH: 400200 2017-12-08 13:39:55 <RMT> NASN_10242: Received: Malformed AS_PATH: 400200 Which in the past meant somebody had a cisco, and wasn't doing no bgp enforce-first-as as BIRD doesn't insert the MICE AS into the AS path, and that confuses Cisco devices. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 8, 2017

Attribute Length Error today

by Frank Bulk

Anyone else see this today with both MICE route reflectors? Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) Dec 8 13:38:56 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Dec 8 13:39:47 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Dec 8 13:39:49 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Dec 8 13:41:28 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Attribute Length Error) Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Dec 8 13:41:36 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Attribute Length Error) Dec 8 13:44:36 192.168.0.85 BGP: Peer 206.108.255.1 UP (ESTABLISHED) Dec 8 13:45:23 192.168.0.85 BGP: Peer 206.108.255.2 UP (ESTABLISHED) Frank

Dec. 8, 2017

Re: SDN Communications Upgrade

by Jeremy Lumby

Correct Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington MN 55425 Main 612-355-7740 Direct 612-392-6814 EFax 952-873-7425 jlumby(a)mnvoip.com -------- Original message -------- From: Richard Laager <rlaager(a)WIKTEL.COM> Date: 12/7/17 12:30 PM (GMT-06:00) To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] SDN Communications Upgrade _____ >From : Richard Laager [rlaager(a)WIKTEL.COM] To : MICE-DISCUSS(a)LISTS.IPHOUSE.NET [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] Date : Thursday, December 7 2017 12:30:33 On 12/05/2017 03:38 PM, Jason Hanke wrote: > SDN is upgrading their connection to 20g from 10G. > > Please use Ethernet5/5 on the Main Switch to SDN. This will be Po19, I presume? -- Richard

Dec. 7, 2017