4 ms·
No, at this level, connections are symetric. The next question is probably why is it reported as 2x2x100G? That's most likely two separate connections which are
by toast0 5y ago
No, at this level, connections are symetric. The next question is probably why is it reported as 2x2x100G? That's most likely two separate connections which are each an aggregated connection of two 100G connections. This is likely to two separate routers on the Starlink.
- jpgvm 5y agoMore importantly it's probably to 2 redundant routers on SIX side also so that both can handle HW failure. On the SIX side the ports are probably already in a redundant chassis but having 2 ports probably still scores you connections to two fully independent chassis in different failure zones.
- kloch 5y agoThe last time I got a tour of the SIX, there were switches on two different floors in the Westin building. This is more for capacity than redundancy. The original location is literally a janitor's closet in a hallway and it's so tight that exhaust fans are built into the door. The second location was in proper four-post racks in a small room. It is possible they have ports on both switches for redundancy but more likely both are on the newer location. The SIX is also built into other buildings and they could connect to more than one, but there is typically only 200G backhaul to the other sites. https://www.seattleix.net/topology https://www.seattleix.net/topology 2x100G to an IX are usually connected as separate ports, each with their own assigned IP ont he IX subnet. BGP multipath can enable load balancing across both ports. Otherwise you might have some peers configured on one port and others on the second. These days I like to have all peers on both ports and use BGP multipath. If both ports are connected to a single switch on the IX side and the same router on the customer side then LACP can be used to combine them into a single 200G port with one IP. This is a less common configuration unless you are doing more than two ports (4x100G as 2x 2x100G lags for example). There is another consideration: what happens if there is an icmp or arp flood on the IX? It's not supposed to happen but sometimes it does, even on the most major and well-run exchanges. In that case you might want to have all of your IX ports on one of your routers, keeping the other one "clean", just in case your control plane policing doesn't mitigate it. Different networks place different priority on IX ports. In most cases it's ok if it's down for a short time (traffic will just shift to paid transit) so redundancy is not essential. In other cases it may be too much traffic to reroute so you care more about IX reliability and redundancy.
- jpgvm 5y agoJust want to say really great summary. I know these things but I bet many folks reading this glean an insight or two. Been a lot time since I have done all this stuff though. I sort of miss it sometimes (though not the pager that comes with the territory).
- throw0101a 5y ago> More importantly it's probably to 2 redundant routers on SIX side also so that both can handle HW failure. Strictly speaking, IXPs do not work at OSI Layer 3, but usually at Layer 2. All the Layer 3 routing logic happens in the routers of the members/customers of the IXP. The IXP is just there to provide a neutral interconnect to everyone without any filtering or policy. The IXP runs router reflectors where people can choose to advertise themselves, and then other folks see who is in the neighbourhood and make their own routing policy choices. The folks at Network Startup Resource Center (NSRC) have a series of videos on "IXP Design and Implementation": * https://learn.nsrc.org/bgp https://learn.nsrc.org/bgp They're by Philip Smith, who helped set up LINX (London, UK) in the early days: * https://nsrc.org/bios/PhilipSmith.html https://nsrc.org/bios/PhilipSmith.html
- martyvis 5y agoThis shows there are 4 BGP peers at SIX https://bgp.he.net/AS14593#_ix https://bgp.he.net/AS14593#_ix
- deleted 5y ago[deleted]
- kloch 5y agoTwo of those are on the normal vlan, and two are on the jumbo frames vlan. Both vlans are available on the same physical ports. Confusingly they list each of those as 200G capacity, not sure if that's a typo or it really is 2x 2x100G. https://peeringdb.com/net/18747 https://peeringdb.com/net/18747
- walrus01 5y ago200G because it's two 100GbE ports in 802.3ad link aggregation
- throw0101a 5y ago> The next question is probably why is it reported as 2x2x100G? At a certain size you don't want 1x100G in case one link breaks, so for a large company they get 2x100G with each fibre going to a separate router. If one router goes down (planned or unplanned) you don't go offline. So now they probably added a second redundant pair. You can see SIX's gear here: * https://www.seattleix.net/topology https://www.seattleix.net/topology They have two Arista 7500-series chassis switches, one 8U and the other 12U (amongst other things): * https://www.arista.com/assets/data/pdf/Datasheets/7500RDataSheet.pdf https://www.arista.com/assets/data/pdf/Datasheets/7500RDataS... One of the line card options is 7500R-36CQ, which can handle thirty-six 100G ports.
- shaklee3 5y agoand the biggest chassis can handle 12 of those cards.
- throw0101a 5y agoThe 7512R at SIX can handle 12. Arista has a 7516R that can hold 16 cards, for a total of 576 100GbE ports. That's not even Arista's highest capacity switch; the 7816R3 can handle 576x400G: * https://www.arista.com/en/products/platforms https://www.arista.com/en/products/platforms (I'm sure other vendors have similar product offerings.)