June 2020 - mice-discuss - lists.micemn.net

Re: Fiber Cut?

by Ben Wiechman

FYI *Tue Jun 30 01:27:26 GMT 2020* Current Update Construction crew is laying a temporary fiber out to repair 3/4 mile. Crews are digging on both sides of the damage to gain access to the fiber. Jairo Palacios *Tue Jun 30 00:35:21 GMT 2020* Current Update Construction crews are on site and they are digging to expose the fiber. Splicer are on location waiting for the construction crew to finish so they can pepping the fiber to splice. No ETR Jairo Palacios. *Tue Jun 30 00:28:51 GMT 2020* Current Update Construction crews are on site and they are digging to expose the fiber. Splicer are on location waiting for the construction crew to finish so they can pepping the fiber to splice. No ETR Ben Wiechman Director of IP Strategy and Engineering Direct: 320.256.0184 Cell: 320.247.3224 ben.wiechman(a)arvig.com 150 Second Street SW | Perham, MN 56573 | arvig.com On Mon, Jun 29, 2020, 16:40 Aaron Clark <aaron(a)futuretech.net> wrote: > We are also seeing a fiber outage with Zayo on a transport circuit between > Omaha and Fremont Nebraska. Still waiting for a call back form support. > It went down at 4:00CST. > > > > Thank you > > Aaron Clark | Vice President – COO > > *Future Technologies* > > *www.futuretech.net <http://www.futuretech.net>* > > *Office: 402.817.2682x121* > > *Mobile: 402.770.9251* > > [image: cid:image001.png@01D36053.05503150] > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Ben > Wiechman > *Sent:* Monday, June 29, 2020 4:34 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] Fiber Cut? > > > > Is anyone riding the Zayo fiber toward Omaha? > > > > We're seeing what appears to be a fiber cut about 35,000' west/south of > Fremont toward Omaha. Does anyone know of anything that might be happening > in that area? > > > > *Ben Wiechman* > > Director of IP Strategy and Engineering > > 320.247.3224 | ben.wiechman(a)arvig.com > > Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com > > > > > ------------------------------ > > 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 >

June 30, 2020

Re: Fiber Cut?

by Aaron Clark

We are also seeing a fiber outage with Zayo on a transport circuit between Omaha and Fremont Nebraska. Still waiting for a call back form support. It went down at 4:00CST. Thank you Aaron Clark | Vice President – COO *Future Technologies* *www.futuretech.net <www.futuretech.net>* *Office: 402.817.2682x121* *Mobile: 402.770.9251* [image: cid:image001.png@01D36053.05503150] *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Ben Wiechman *Sent:* Monday, June 29, 2020 4:34 PM *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* [MICE-DISCUSS] Fiber Cut? Is anyone riding the Zayo fiber toward Omaha? We're seeing what appears to be a fiber cut about 35,000' west/south of Fremont toward Omaha. Does anyone know of anything that might be happening in that area? *Ben Wiechman* Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

June 29, 2020

Fiber Cut?

by Ben Wiechman

Is anyone riding the Zayo fiber toward Omaha? We're seeing what appears to be a fiber cut about 35,000' west/south of Fremont toward Omaha. Does anyone know of anything that might be happening in that area? Ben Wiechman Director of IP Strategy and Engineering 320.247.3224 | ben.wiechman(a)arvig.com Arvig | 224 East Main Street | Melrose, MN 56352 | arvig.com

June 29, 2020

Strange log line in my router related to MICE route reflector #2

by Frank Bulk

Can anyone decipher what this log line on my Arista means? Jun 26 03:18:58 207.32.15.14 (sxct-north-2.sxcy.fbnt.netins.net) Rib: mpbgp_recv_mpreach: peer 2001:504:27::d1af:0:2 (AS53679-RR-2.micemn.net) (AS 53679 MICEASN, US) link-local next hop fe80::e2ac:f1ef:fe4b:d93b%65536 improper, ignoring this next-hop Frank AS18883

June 26, 2020

Re: IRR Filtering

by Austin Gillmann

I just noticed you can also lookup your range against HE filter and it'll tell you wether it passes or not (as well as fully explaining the filters conditions.) Decent for double checking if the rules are working and why if not Link is at https://routing.he.net note that it can take awhile to load after querying a range On Tue, Jun 23, 2020 at 2:15 PM Richard Laager <rlaager(a)wiktel.com> wrote: > On 6/23/20 2:03 PM, Andrew Hoyos wrote: > > AUT-NUM for your ASN with an export line matching your as-set (ie: > > export: to ANY announce AS65535-AS-SET-OBJECT) > > This look reasonable as a starting point? > > import: from AS-ANY accept ANY > export: to AS-ANY announce AS-WIKTEL > mp-import: afi ipv6.unicast from AS-ANY accept ANY > mp-export: afi ipv6.unicast to AS-ANY announce AS-WIKTEL > > -- > Richard >

June 25, 2020

Re: IRR Filtering

by Richard Laager

On 6/23/20 2:03 PM, Andrew Hoyos wrote: > AUT-NUM for your ASN with an export line matching your as-set (ie: > export: to ANY announce AS65535-AS-SET-OBJECT) This look reasonable as a starting point? import: from AS-ANY accept ANY export: to AS-ANY announce AS-WIKTEL mp-import: afi ipv6.unicast from AS-ANY accept ANY mp-export: afi ipv6.unicast to AS-ANY announce AS-WIKTEL -- Richard

June 23, 2020

Re: IRR Filtering

by Andrew Hoyos

HE.net <http://he.net/> will parse out your AS-SET or export: line in AUT-NUM object. See: http://routing.he.net/algorithm.html <http://routing.he.net/algorithm.html> Ideally, best case, you have: AS-SET including your ASN and your downstream customers (if any) ROUTE objects created for each prefix with origin set to the correct ASN AUT-NUM for your ASN with an export line matching your as-set (ie: export: to ANY announce AS65535-AS-SET-OBJECT) If you haven’t also update PeeringDB.com <http://peeringdb.com/> with your as-set info. > On Jun 23, 2020, at 1:53 PM, Larry Larsen <llarsen(a)LONGLINES.BIZ> wrote: > > Good Afternoon; > > I am also using ARIN IRR and have setup an AUT-NUM object. I was told that I had to set it up to get updates to appear properly. The problem I have is not with my IP Addresses, but with my customers that have their own blocks and ASNs. HE is still rejecting them. I am not sure how to get the AUT-NUM or Route-Set to work for my customers. > > Thank you! > > Larry L. Larsen > Director of Information Technology > O: 712-271-5920 | F: 712-271-2727 > llarsen(a)longlines.biz > > > Connect | Empower | Erich > > 504 4th Street | Sergeant Bluff, IA 51054 > www.longlines.com > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager > Sent: Tuesday, June 23, 2020 1:44 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] IRR Filtering > > WARNING!! This message originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. > > Context: Hurricane Electric is now doing IRR filtering now. My question isn't specific to HE's filtering, but is more about what the best practices are. > > I'm looking for clue, on or off list, about whether my AS should have an aut-num object. We already have an as-set object listing our AS as well as those of our transit customers. This as-set's name is listed in PeeringDB. We also already have a route-set object containing route objects for each of our prefixes. > > I've looked at some other networks and this approach (list an as-set in > PeeringDB) seems to be the common case. I am only aware of a couple networks who are using an aut-num object. > > I'm cool with creating an aut-num object, but how much do I really need to fill in? That is, do I need to have import/export statements for literally every AS I peer with, or can I just use "from ANY accept ANY" > and "to ANY announce AS-WIKTEL"? I don't want to create and have to maintain an aut-num that is more complex than necessary. I also don't want to break working traffic with peers who might pick up that aut-num object automatically. > > If it matters, I use the ARIN IRR. I was previously using email templates but would intend to switch (which I understand is permanent) to the web interface on my next modification. > > -- > Richard

June 23, 2020

Re: IRR Filtering

by Larry Larsen

Good Afternoon; I am also using ARIN IRR and have setup an AUT-NUM object. I was told that I had to set it up to get updates to appear properly. The problem I have is not with my IP Addresses, but with my customers that have their own blocks and ASNs. HE is still rejecting them. I am not sure how to get the AUT-NUM or Route-Set to work for my customers. Thank you! Larry L. Larsen Director of Information Technology O: 712-271-5920 | F: 712-271-2727 llarsen(a)longlines.biz Connect | Empower | Erich 504 4th Street | Sergeant Bluff, IA 51054 www.longlines.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Tuesday, June 23, 2020 1:44 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] IRR Filtering WARNING!! This message originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Context: Hurricane Electric is now doing IRR filtering now. My question isn't specific to HE's filtering, but is more about what the best practices are. I'm looking for clue, on or off list, about whether my AS should have an aut-num object. We already have an as-set object listing our AS as well as those of our transit customers. This as-set's name is listed in PeeringDB. We also already have a route-set object containing route objects for each of our prefixes. I've looked at some other networks and this approach (list an as-set in PeeringDB) seems to be the common case. I am only aware of a couple networks who are using an aut-num object. I'm cool with creating an aut-num object, but how much do I really need to fill in? That is, do I need to have import/export statements for literally every AS I peer with, or can I just use "from ANY accept ANY" and "to ANY announce AS-WIKTEL"? I don't want to create and have to maintain an aut-num that is more complex than necessary. I also don't want to break working traffic with peers who might pick up that aut-num object automatically. If it matters, I use the ARIN IRR. I was previously using email templates but would intend to switch (which I understand is permanent) to the web interface on my next modification. -- Richard

June 23, 2020

IRR Filtering

by Richard Laager

Context: Hurricane Electric is now doing IRR filtering now. My question isn't specific to HE's filtering, but is more about what the best practices are. I'm looking for clue, on or off list, about whether my AS should have an aut-num object. We already have an as-set object listing our AS as well as those of our transit customers. This as-set's name is listed in PeeringDB. We also already have a route-set object containing route objects for each of our prefixes. I've looked at some other networks and this approach (list an as-set in PeeringDB) seems to be the common case. I am only aware of a couple networks who are using an aut-num object. I'm cool with creating an aut-num object, but how much do I really need to fill in? That is, do I need to have import/export statements for literally every AS I peer with, or can I just use "from ANY accept ANY" and "to ANY announce AS-WIKTEL"? I don't want to create and have to maintain an aut-num that is more complex than necessary. I also don't want to break working traffic with peers who might pick up that aut-num object automatically. If it matters, I use the ARIN IRR. I was previously using email templates but would intend to switch (which I understand is permanent) to the web interface on my next modification. -- Richard

June 23, 2020

Re: Please Welcome SaskTel (AS803) to MICE!

by Doug McIntyre

On Fri, Jun 19, 2020 at 12:30:58PM -0500, Jay Hanke wrote: >Name: Saskatchewan Telecommunications >Port: Main Switch Ethernet 3/24/1 >ASN: 803 >IPv4: 206.108.255.166/24 >IPv6: 2001:504:27:0:0:0323::1/64 >Peering Contact: carrier.quotes(a)sasktel.com >Route Servers- YES >BFD: No Added into the route-servers and ready to go. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

June 19, 2020