March 2021 - Discuss

SLIX EdgeConneX SLC01 Maintenance 2021/03/23 05:00AM MDT
by Pete Ashdown 22 Mar '21

22 Mar '21

When: March 23, 2021 Maintenance Window: 05:00 AM MDT - 06:00 AM MDT Where: SLIX EdgeConneX SLC01 The SLIX switches at EdgeConneX SLC01 will have their back-haul rerouted through a new connection. There will be a complete interruption of service, which should ideally be momentary as the VLAN reroutes and the mac-table repopulates. Peers affected are Twitch and Cloudflare.

1 0

PeeringDB login
by Pete Ashdown 06 Mar '21

06 Mar '21

The PeeringDB login should work now if your account is affiliated at PeeringDB with the network peering at SLIX. Let me know if you have trouble.

1 0

VLAN IPv6 mask is /64, not /48
by Pete Ashdown 05 Mar '21

05 Mar '21

An addendum to the below. For the initial VLAN itself, we are going to use an IPv6 mask of /64 instead of /48. The below instructions have been updated to reflect this. * ARIN has delegated SLIX an IPv4 /24 and an IPv6 /48: IPv4: 149.112.13.0/24 IPv6: 2001:504:105::/48 SLIX will use IPv6 2001:504:105::/64 for the first peering VLAN. If you have an existing SLIX IP address at 204.228.158.x, add 10 to it to find your new IP address. To find your new IPv6 address, take this number and make a decimal version of the IPv4 address. For example: 204.228.158.4 + 10 = new IPv4 149.112.13.14/24 & IPv6 = 2001:504:105::14/64 These new subnets are live now on the SLIX infrastructure. There is no need for administrative configuration, simply add the new IP addresses to your SLIX router interface. I would like to remove the old SLIX subnets by June 1, 2021, so please migrate soon.

1 0

Re: 10 Years of SLIX - Upgrades!
by Rob Mosher 05 Mar '21

05 Mar '21

Hello SLIX members, Hurricane Electric AS6939 has renumbered and copied all of our existing sessions to the new addresses. Our new addresses are 149.112.13.31 and 2001:504:105::31 Any existing peers can configure sessions to us at these addresses. If there are any members that wish to setup peering, feel free to email me directly off list. -- Rob Mosher Director of Engineering Hurricane Electric / AS6939 On 3/3/2021 1:54 PM, Pete Ashdown wrote: > This year marks the 10th year of SLIX, Salt Lake Internet eXchange.? > Thank you to all who have made it possible. > > This year also marks the most significant upgrades to the SLIX > infrastructure in its history. > > * ARIN has delegated SLIX an IPv4 /24 and an IPv6 /48: > > IPv4: 149.112.13.0/24 > > IPv6: 2001:504:105::0/48 > > If you have an existing SLIX IP address at 204.228.158.x, add 10 to > it to find your new IP address.? To find your new IPv6 address, take > this number and make a decimal version of the IPv4 address.? For > example: > > 204.228.158.4 + 10 = new IPv4 149.112.13.14/24 & IPv6 = > 2001:504:105::14/48 > > These new subnets are live now on the SLIX infrastructure.? There is > no need for admistrative configuration, simply add the new IP > addresses to your SLIX router interface.? I would like to remove the > old SLIX subnets by June 1, 2021, so please migrate soon. > > * SLIX has installed IXP Manager with redundant route-servers, > route-collector, and an as112 service. > > Use your PeeringDB.com login or contact us for an account to login to: > > https://ixp.slix.net > > Your account will need to be administratively associated with your > customer/peering entry after this is done.? Once associated, you can > inspect what your SLIX BGP view is of your announcements with the > route-collector (rc1) looking glass.? When you are satisfied that > this is ready, I can add you to the route-servers to peer with > everyone else.? You can also continue to peer directly with other > SLIX peers, but they will need to change their IP address to the new > subnet. > > For those of you who are unfamiliar with a route-server, it > essentially offloads all the work of peering at an exchange and > intelligently filters for you.? The SLIX route-collector provides a > view of your announcements without sending them to anyone else.? > Both the route-servers and route-collectors are IRR filtered with > RPKI validation.? They update repeatedly throughout the day. > > In order to utilize the AS112 service, you either need to peer with > the route-servers, or request direct peering with the AS112 IP > addresses. > > * More dark fiber is pending, and equipment has arrived to increase > port capacity to 100Gb. A SLIX 100Gb port is $3000/MRC, with either > payment to SLIX for a QSFP of your choice, or send us one. If you > are interested in upgrading to a 100Gb port, or multiples, please > let us know. > > * Mailman has been been upgraded to Mailman3 > <https://slix.net/mailman3/postorius/lists/>. > > * Follow us on Twitter <https://twitter.com/saltlakeix> and like our > page on Facebook <https://www.facebook.com/saltlakeix>! > > > Please let us know if you have any questions, issues or problems.? > Here's to open packet exchange in the decades to come! > > > _______________________________________________ > Discuss mailing list -- discuss(a)slix.net > To unsubscribe send an email to discuss-leave(a)slix.net

1 0

10 Years of SLIX - Upgrades!
by Pete Ashdown 03 Mar '21

03 Mar '21

This year marks the 10th year of SLIX, Salt Lake Internet eXchange. Thank you to all who have made it possible. This year also marks the most significant upgrades to the SLIX infrastructure in its history. * ARIN has delegated SLIX an IPv4 /24 and an IPv6 /48: IPv4: 149.112.13.0/24 IPv6: 2001:504:105::0/48 If you have an existing SLIX IP address at 204.228.158.x, add 10 to it to find your new IP address. To find your new IPv6 address, take this number and make a decimal version of the IPv4 address. For example: 204.228.158.4 + 10 = new IPv4 149.112.13.14/24 & IPv6 = 2001:504:105::14/48 These new subnets are live now on the SLIX infrastructure. There is no need for admistrative configuration, simply add the new IP addresses to your SLIX router interface. I would like to remove the old SLIX subnets by June 1, 2021, so please migrate soon. * SLIX has installed IXP Manager with redundant route-servers, route-collector, and an as112 service. Use your PeeringDB.com login or contact us for an account to login to: https://ixp.slix.net Your account will need to be administratively associated with your customer/peering entry after this is done. Once associated, you can inspect what your SLIX BGP view is of your announcements with the route-collector (rc1) looking glass. When you are satisfied that this is ready, I can add you to the route-servers to peer with everyone else. You can also continue to peer directly with other SLIX peers, but they will need to change their IP address to the new subnet. For those of you who are unfamiliar with a route-server, it essentially offloads all the work of peering at an exchange and intelligently filters for you. The SLIX route-collector provides a view of your announcements without sending them to anyone else. Both the route-servers and route-collectors are IRR filtered with RPKI validation. They update repeatedly throughout the day. In order to utilize the AS112 service, you either need to peer with the route-servers, or request direct peering with the AS112 IP addresses. * More dark fiber is pending, and equipment has arrived to increase port capacity to 100Gb. A SLIX 100Gb port is $3000/MRC, with either payment to SLIX for a QSFP of your choice, or send us one. If you are interested in upgrading to a 100Gb port, or multiples, please let us know. * Mailman has been been upgraded to Mailman3 <https://slix.net/mailman3/postorius/lists/>. * Follow us on Twitter <https://twitter.com/saltlakeix> and like our page on Facebook <https://www.facebook.com/saltlakeix>! Please let us know if you have any questions, issues or problems. Here's to open packet exchange in the decades to come!

1 1