- mice-discuss - lists.micemn.net

Re: route server down?

by Steve Savoy

I am running Brocade as well. Steve Savoy WCTA Sent from my iPhone > On Apr 30, 2020, at 8:26 AM, James Urwiller <james.urwiller(a)turnkey-telecom.com> wrote: > > I am running brocade, yes. > > James Urwiller > Network Architect > Stealth Broadband > james.urwiller(a)stealthbroadband.com > > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke > Sent: Thursday, April 30, 2020 08:24 > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] route server down? > > I emailed xcel about the invalid next-hop address. > > We should filter invalid next hops on the route servers. > > There also appears to be an issue with how some routers handle the invalid > next hop. > > Are all the peers with the issue of losing the session to RS2 running > Brocade? > >> On Thu, Apr 30, 2020 at 8:17 AM David Farmer <farmer(a)umn.edu> wrote: >> >> someone with Access should see what route server 2 sees for that prefix, >> and maybe kick it over after look at it. >> >>> On Thu, Apr 30, 2020 at 8:04 AM Jay Hanke <jayhanke(a)southfront.io> wrote: >>> >>> We're seeing the same with a good next-hop from RS1. >>> >>> On Thu, Apr 30, 2020 at 7:55 AM Chris Wopat <wopat(a)wiscnet.net> wrote: >>>> >>>> On 4/30/20 7:49 AM, David Farmer wrote: >>>> >>>>> We're running IOS XR, I found these droppings in our logs; >>>>> >>>> >>>> RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: >>>> %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received >>>> from neighbor 206.108.255.2 (VRF: default) - message length 59 >>>> bytes, error flags 0x00000200, action taken "TreatAsWdr". Error >>>> details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags >>>> 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] >>>> 198.179.154.0/23 RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: >>>> %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received >>>> from neighbor 206.108.255.2 (VRF: default) - message length 59 >>>> bytes, error flags 0x00000200, action taken "TreatAsWdr". Error >>>> details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags >>>> 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] >>>> 198.179.154.0/23 >>>>> >>>>> Maybe try resting you BGP sessions. >>>>> >>>> We're seeing a weird next-hop ip on that prefix (rfc1918) and its >>>> hidden on our net. >>>> >>>> Is 10.223.129.2 something internal to route server #2? >>>> >>>>> show route 198.179.154.0 hidden detail >>>> >>>> inet.0: 795967 destinations, 2081403 routes (795589 active, 0 >>>> holddown, >>>> 1604 hidden) >>>> 198.179.154.0/23 (3 entries, 1 announced) >>>> BGP >>>> Next hop type: Router, Next hop index: 0 >>>> Address: 0x113614cc >>>> Next-hop reference count: 1 >>>> Source: 206.108.255.2 >>>> Next hop: 10.223.129.2 via xe-0/1/5.300, selected >>>> Session Id: 0x0 >>>> State: <Hidden Ext> >>>> Inactive reason: Unusable path >>>> Local AS: 65400 Peer AS: 53679 >>>> Age: 10:02:05 >>>> Validation State: unverified >>>> Task: BGP_53679.206.108.255.2 >>>> AS path: I >>>> Communities: target:21693:1000 >>>> Router ID: 206.108.255.2 >>>> Hidden reason: protocol nexthop is not on the >>>> interface >>>> >>>> >>>> -- >>>> Chris Wopat >>>> Network Engineer, WiscNet >>>> wopat(a)wiscnet.net 608-210-3965 >>> >>> >>> >>> -- >>> Jay Hanke, President >>> South Front Networks >>> jayhanke(a)southfront.io >>> Phone 612-204-0000 >> >> >> >> -- >> =============================================== >> David Farmer Email:farmer@umn.edu >> Networking & Telecommunication Services Office of Information >> Technology University of Minnesota >> 2218 University Ave SE Phone: 612-626-0815 >> Minneapolis, MN 55414-3029 Cell: 612-812-9952 >> =============================================== >> >> ________________________________ >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

April 30, 2020

Re: route server down?

by James Urwiller

I am running brocade, yes. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Thursday, April 30, 2020 08:24 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] route server down? I emailed xcel about the invalid next-hop address. We should filter invalid next hops on the route servers. There also appears to be an issue with how some routers handle the invalid next hop. Are all the peers with the issue of losing the session to RS2 running Brocade? On Thu, Apr 30, 2020 at 8:17 AM David Farmer <farmer(a)umn.edu> wrote: > > someone with Access should see what route server 2 sees for that prefix, > and maybe kick it over after look at it. > > On Thu, Apr 30, 2020 at 8:04 AM Jay Hanke <jayhanke(a)southfront.io> wrote: >> >> We're seeing the same with a good next-hop from RS1. >> >> On Thu, Apr 30, 2020 at 7:55 AM Chris Wopat <wopat(a)wiscnet.net> wrote: >> > >> > On 4/30/20 7:49 AM, David Farmer wrote: >> > >> > > We're running IOS XR, I found these droppings in our logs; >> > > >> > >> > RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: >> > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received >> > from neighbor 206.108.255.2 (VRF: default) - message length 59 >> > bytes, error flags 0x00000200, action taken "TreatAsWdr". Error >> > details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags >> > 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] >> > 198.179.154.0/23 RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: >> > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received >> > from neighbor 206.108.255.2 (VRF: default) - message length 59 >> > bytes, error flags 0x00000200, action taken "TreatAsWdr". Error >> > details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags >> > 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] >> > 198.179.154.0/23 >> > > >> > > Maybe try resting you BGP sessions. >> > > >> > We're seeing a weird next-hop ip on that prefix (rfc1918) and its >> > hidden on our net. >> > >> > Is 10.223.129.2 something internal to route server #2? >> > >> > > show route 198.179.154.0 hidden detail >> > >> > inet.0: 795967 destinations, 2081403 routes (795589 active, 0 >> > holddown, >> > 1604 hidden) >> > 198.179.154.0/23 (3 entries, 1 announced) >> > BGP >> > Next hop type: Router, Next hop index: 0 >> > Address: 0x113614cc >> > Next-hop reference count: 1 >> > Source: 206.108.255.2 >> > Next hop: 10.223.129.2 via xe-0/1/5.300, selected >> > Session Id: 0x0 >> > State: <Hidden Ext> >> > Inactive reason: Unusable path >> > Local AS: 65400 Peer AS: 53679 >> > Age: 10:02:05 >> > Validation State: unverified >> > Task: BGP_53679.206.108.255.2 >> > AS path: I >> > Communities: target:21693:1000 >> > Router ID: 206.108.255.2 >> > Hidden reason: protocol nexthop is not on the >> > interface >> > >> > >> > -- >> > Chris Wopat >> > Network Engineer, WiscNet >> > wopat(a)wiscnet.net 608-210-3965 >> >> >> >> -- >> Jay Hanke, President >> South Front Networks >> jayhanke(a)southfront.io >> Phone 612-204-0000 > > > > -- > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services Office of Information > Technology University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

April 30, 2020

Re: route server down?

by Jay Hanke

I emailed xcel about the invalid next-hop address. We should filter invalid next hops on the route servers. There also appears to be an issue with how some routers handle the invalid next hop. Are all the peers with the issue of losing the session to RS2 running Brocade? On Thu, Apr 30, 2020 at 8:17 AM David Farmer <farmer(a)umn.edu> wrote: > > someone with Access should see what route server 2 sees for that prefix, and maybe kick it over after look at it. > > On Thu, Apr 30, 2020 at 8:04 AM Jay Hanke <jayhanke(a)southfront.io> wrote: >> >> We're seeing the same with a good next-hop from RS1. >> >> On Thu, Apr 30, 2020 at 7:55 AM Chris Wopat <wopat(a)wiscnet.net> wrote: >> > >> > On 4/30/20 7:49 AM, David Farmer wrote: >> > >> > > We're running IOS XR, I found these droppings in our logs; >> > > >> > >> > RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: >> > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from >> > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error >> > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error >> > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data >> > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 >> > RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: >> > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from >> > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error >> > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error >> > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data >> > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 >> > > >> > > Maybe try resting you BGP sessions. >> > > >> > We're seeing a weird next-hop ip on that prefix (rfc1918) and its hidden >> > on our net. >> > >> > Is 10.223.129.2 something internal to route server #2? >> > >> > > show route 198.179.154.0 hidden detail >> > >> > inet.0: 795967 destinations, 2081403 routes (795589 active, 0 holddown, >> > 1604 hidden) >> > 198.179.154.0/23 (3 entries, 1 announced) >> > BGP >> > Next hop type: Router, Next hop index: 0 >> > Address: 0x113614cc >> > Next-hop reference count: 1 >> > Source: 206.108.255.2 >> > Next hop: 10.223.129.2 via xe-0/1/5.300, selected >> > Session Id: 0x0 >> > State: <Hidden Ext> >> > Inactive reason: Unusable path >> > Local AS: 65400 Peer AS: 53679 >> > Age: 10:02:05 >> > Validation State: unverified >> > Task: BGP_53679.206.108.255.2 >> > AS path: I >> > Communities: target:21693:1000 >> > Router ID: 206.108.255.2 >> > Hidden reason: protocol nexthop is not on the interface >> > >> > >> > -- >> > Chris Wopat >> > Network Engineer, WiscNet >> > wopat(a)wiscnet.net 608-210-3965 >> >> >> >> -- >> Jay Hanke, President >> South Front Networks >> jayhanke(a)southfront.io >> Phone 612-204-0000 > > > > -- > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

April 30, 2020

Re: route server down?

by David Farmer

someone with Access should see what route server 2 sees for that prefix, and maybe kick it over after look at it. On Thu, Apr 30, 2020 at 8:04 AM Jay Hanke <jayhanke(a)southfront.io> wrote: > We're seeing the same with a good next-hop from RS1. > > On Thu, Apr 30, 2020 at 7:55 AM Chris Wopat <wopat(a)wiscnet.net> wrote: > > > > On 4/30/20 7:49 AM, David Farmer wrote: > > > > > We're running IOS XR, I found these droppings in our logs; > > > > > > > RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: > > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from > > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error > > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error > > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data > > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 > > RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: > > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from > > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error > > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error > > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data > > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 > > > > > > Maybe try resting you BGP sessions. > > > > > We're seeing a weird next-hop ip on that prefix (rfc1918) and its hidden > > on our net. > > > > Is 10.223.129.2 something internal to route server #2? > > > > > show route 198.179.154.0 hidden detail > > > > inet.0: 795967 destinations, 2081403 routes (795589 active, 0 holddown, > > 1604 hidden) > > 198.179.154.0/23 (3 entries, 1 announced) > > BGP > > Next hop type: Router, Next hop index: 0 > > Address: 0x113614cc > > Next-hop reference count: 1 > > Source: 206.108.255.2 > > Next hop: 10.223.129.2 via xe-0/1/5.300, selected > > Session Id: 0x0 > > State: <Hidden Ext> > > Inactive reason: Unusable path > > Local AS: 65400 Peer AS: 53679 > > Age: 10:02:05 > > Validation State: unverified > > Task: BGP_53679.206.108.255.2 > > AS path: I > > Communities: target:21693:1000 > > Router ID: 206.108.255.2 > > Hidden reason: protocol nexthop is not on the interface > > > > > > -- > > Chris Wopat > > Network Engineer, WiscNet > > wopat(a)wiscnet.net 608-210-3965 > > > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

April 30, 2020

Re: route server down?

by Jay Hanke

We're seeing the same with a good next-hop from RS1. On Thu, Apr 30, 2020 at 7:55 AM Chris Wopat <wopat(a)wiscnet.net> wrote: > > On 4/30/20 7:49 AM, David Farmer wrote: > > > We're running IOS XR, I found these droppings in our logs; > > > > RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 > RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 > > > > Maybe try resting you BGP sessions. > > > We're seeing a weird next-hop ip on that prefix (rfc1918) and its hidden > on our net. > > Is 10.223.129.2 something internal to route server #2? > > > show route 198.179.154.0 hidden detail > > inet.0: 795967 destinations, 2081403 routes (795589 active, 0 holddown, > 1604 hidden) > 198.179.154.0/23 (3 entries, 1 announced) > BGP > Next hop type: Router, Next hop index: 0 > Address: 0x113614cc > Next-hop reference count: 1 > Source: 206.108.255.2 > Next hop: 10.223.129.2 via xe-0/1/5.300, selected > Session Id: 0x0 > State: <Hidden Ext> > Inactive reason: Unusable path > Local AS: 65400 Peer AS: 53679 > Age: 10:02:05 > Validation State: unverified > Task: BGP_53679.206.108.255.2 > AS path: I > Communities: target:21693:1000 > Router ID: 206.108.255.2 > Hidden reason: protocol nexthop is not on the interface > > > -- > Chris Wopat > Network Engineer, WiscNet > wopat(a)wiscnet.net 608-210-3965 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

April 30, 2020

Re: route server down?

by David Farmer

On Thu, Apr 30, 2020 at 7:55 AM Chris Wopat <wopat(a)wiscnet.net> wrote: > On 4/30/20 7:49 AM, David Farmer wrote: > > > We're running IOS XR, I found these droppings in our logs; > > > > RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 > RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: > %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from > neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error > flags 0x00000200, action taken "TreatAsWdr". Error details: "Error > 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data > [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 > > > > Maybe try resting you BGP sessions. > > > We're seeing a weird next-hop ip on that prefix (rfc1918) and its hidden > on our net. > > Is 10.223.129.2 something internal to route server #2? > > > show route 198.179.154.0 hidden detail > > inet.0: 795967 destinations, 2081403 routes (795589 active, 0 holddown, > 1604 hidden) > 198.179.154.0/23 (3 entries, 1 announced) > BGP > Next hop type: Router, Next hop index: 0 > Address: 0x113614cc > Next-hop reference count: 1 > Source: 206.108.255.2 > Next hop: 10.223.129.2 via xe-0/1/5.300, selected > Session Id: 0x0 > State: <Hidden Ext> > Inactive reason: Unusable path > Local AS: 65400 Peer AS: 53679 > Age: 10:02:05 > Validation State: unverified > Task: BGP_53679.206.108.255.2 > AS path: I > Communities: target:21693:1000 > Router ID: 206.108.255.2 > Hidden reason: protocol nexthop is not on the interface > Here is what I see; BGP routing table entry for 198.179.154.0/23 Versions: Process bRIB/RIB SendTblVer Speaker 14008256 14008256 Last Modified: Apr 29 21:50:26.404 for 10:08:07 Paths: (1 available, best #1) Advertised IPv4 Unicast paths to update-groups (with more than one peer): 1.2 1.7 1.11 1.18 Advertised IPv4 Unicast paths to peers (in unique update groups): 146.57.254.0 146.57.252.9 146.57.252.217 146.57.248.131 146.57.253.81 146.57.253.9 146.57.253.157 146.57.255.184 Path #1: Received by speaker 1 Advertised IPv4 Unicast paths to update-groups (with more than one peer): 1.2 1.7 1.11 1.18 Advertised IPv4 Unicast paths to peers (in unique update groups): 146.57.254.0 146.57.252.9 146.57.252.217 146.57.248.131 146.57.253.81 146.57.253.9 146.57.253.157 146.57.255.184 21693 206.108.255.115 from 206.108.255.1 (206.108.255.1) Origin IGP, localpref 180, valid, external, best, group-best, import-candidate Received Path ID 0, Local Path ID 1, version 14008256 Community: 57:12 57:10500 57:10505 Extended community: RT:21693:1000 Origin-AS validity: not-found It is an Xcel Energy Prefix, which jives with ARIN; -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

April 30, 2020

Re: route server down?

by Chris Wopat

On 4/30/20 7:49 AM, David Farmer wrote: > We're running IOS XR, I found these droppings in our logs; > RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error flags 0x00000200, action taken "TreatAsWdr". Error details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error flags 0x00000200, action taken "TreatAsWdr". Error details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 > > Maybe try resting you BGP sessions. > We're seeing a weird next-hop ip on that prefix (rfc1918) and its hidden on our net. Is 10.223.129.2 something internal to route server #2? > show route 198.179.154.0 hidden detail inet.0: 795967 destinations, 2081403 routes (795589 active, 0 holddown, 1604 hidden) 198.179.154.0/23 (3 entries, 1 announced) BGP Next hop type: Router, Next hop index: 0 Address: 0x113614cc Next-hop reference count: 1 Source: 206.108.255.2 Next hop: 10.223.129.2 via xe-0/1/5.300, selected Session Id: 0x0 State: <Hidden Ext> Inactive reason: Unusable path Local AS: 65400 Peer AS: 53679 Age: 10:02:05 Validation State: unverified Task: BGP_53679.206.108.255.2 AS path: I Communities: target:21693:1000 Router ID: 206.108.255.2 Hidden reason: protocol nexthop is not on the interface -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

April 30, 2020

Re: route server down?

by David Farmer

We're running IOS XR, I found these droppings in our logs; RP/0/RP0/CPU0:Apr 29 21:50:26.798 CDT: bgp[1068]: %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error flags 0x00000200, action taken "TreatAsWdr". Error details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 RP/0/RP1/CPU0:Apr 29 21:50:26.797 CDT: bgp[1068]: %ROUTING-BGP-3-MALFORM_UPDATE : Malformed UPDATE message received from neighbor 206.108.255.2 (VRF: default) - message length 59 bytes, error flags 0x00000200, action taken "TreatAsWdr". Error details: "Error 0x00000200, Field "Attr-data", Attribute 2 (Flags 0x40, Length 0), Data [400200]". NLRIs: [IPv4 Unicast] 198.179.154.0/23 Maybe try resting you BGP sessions. On Thu, Apr 30, 2020 at 7:39 AM James Urwiller < james.urwiller(a)turnkey-telecom.com> wrote: > 04-29-21:53:02 CDT for me. > > > > James Urwiller > > Network Architect > > Stealth Broadband > > james.urwiller(a)stealthbroadband.com > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *David > Farmer > *Sent:* Thursday, April 30, 2020 07:36 > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] route server down? > > > > Both our BGP sessions are up and I just pinged them both as well. > > > > > > > > On Thu, Apr 30, 2020 at 7:32 AM Steve Savoy <stevesavoy(a)wctatel.com> > wrote: > > I was wondering the same thing – I show Apr 29 21:50:26. > > > > > > <http://www.wctatel.net/> > > * Steve Savoy* > > * Network Administrator* > > *Winnebago Cooperative Telecom Assn.* > > 704 E Main St | Lake Mills, IA 50450 > > Phone 641.592.6105 | Toll Free 800.592.6105 | Fax 641.592.6067 > > Email stevesavoy(a)wctatel.com > > > > [image: Facebook] <https://www.facebook.com/WCTAtel/> > > [image: YouTube] > <https://www.youtube.com/channel/UCM__0MiAl63zt93t2aKpOXQ> > > > > > > > > > > > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *James > Urwiller > *Sent:* Thursday, April 30, 2020 7:30 AM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] route server down? > > > > Did I miss something or is the 2nd mice route server down since right > before 22:00 CDT last night? > > > > James Urwiller > > Network Architect > > Stealth Broadband > > james.urwiller(a)stealthbroadband.com > > > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > Confidentiality Notice: This correspondence is the property of Winnebago > Cooperative Telecom Association and is for the sole use of the intended > recipient(s) and may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. If you > are not the intended recipient, please contact the sender by reply email > and destroy all copies of the original message. > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > > -- > > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > > > ------------------------------ > > 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 > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

April 30, 2020

Re: route server down?

by James Urwiller

I also have the attribute length error in logs. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Steve Savoy *Sent:* Thursday, April 30, 2020 07:43 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] route server down? My Router shows the following: BGP: Peer (VRF: default-vrf) 206.108.255.2 DOWN (Attribute Length Error) Steve Savoy WCTA *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *James Urwiller *Sent:* Thursday, April 30, 2020 7:40 AM *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] route server down? I can ping it still also, the BGP session changed from established to ACTIV. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *David Farmer *Sent:* Thursday, April 30, 2020 07:36 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] route server down? Both our BGP sessions are up and I just pinged them both as well. On Thu, Apr 30, 2020 at 7:32 AM Steve Savoy <stevesavoy(a)wctatel.com> wrote: I was wondering the same thing – I show Apr 29 21:50:26. <http://www.wctatel.net/> * Steve Savoy* * Network Administrator* *Winnebago Cooperative Telecom Assn.* 704 E Main St | Lake Mills, IA 50450 Phone 641.592.6105 | Toll Free 800.592.6105 | Fax 641.592.6067 Email stevesavoy(a)wctatel.com [image: Facebook] <https://www.facebook.com/WCTAtel/> [image: YouTube] <https://www.youtube.com/channel/UCM__0MiAl63zt93t2aKpOXQ> *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *James Urwiller *Sent:* Thursday, April 30, 2020 7:30 AM *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* [MICE-DISCUSS] route server down? Did I miss something or is the 2nd mice route server down since right before 22:00 CDT last night? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ------------------------------ 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 Confidentiality Notice: This correspondence is the property of Winnebago Cooperative Telecom Association and is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

April 30, 2020

Re: [EXT]: Re: [MICE-DISCUSS] route server down?

by Danny Meister

April 30, 2020