Fabric ports at 10G, 100G or 400G, in LAGs; fabric customers only when they fit
A fabric (NNI) port comes in 10G, 100G or 400G, as fast as the router takes and no faster than 400G, and bundles into a LAG of up to eight members like transit, IX and PNIs. Each member takes a router port (10G on a breakout, a quarter of one) and pays the monthly price; upgrading moves and pays for every member. 10G and 100G keep their prices, 400G is $3,000/mo. A model change that would strand a 400G fabric port is refused, and saves drop fabric ports that make no sense. The NNI requirement counted what the port already carried but not the offer's own bandwidth, so an offer passed as long as the port was not already over and auto-accept took customers that did not fit. It now counts the offer too. Closes #140, closes #307.
This commit is contained in:
parent
4ec3fb4a1a
commit
85701dbb82
22 changed files with 184 additions and 27 deletions
|
|
@ -1017,7 +1017,6 @@
|
|||
"city_panel.pay_a_bigger_network_per_gbps":"Pay a bigger network per Gbps and it carries your traffic to the whole internet. Billed on the 95th percentile of the last 30 days, with a 20% commit and a port fee. Spikes like DDoS raise your bill.",
|
||||
"city_panel.peer_at_ix_without_building_a":"Peer at {ix} without building a POP. Order a virtual circuit here from one of your POPs over {fabs}.",
|
||||
"city_panel.port_cost_mo_mo":"{port} <small>{cost} + {mo}/mo</small>",
|
||||
"city_panel.port_port_price_mo":"{port} port · {price}/mo",
|
||||
"city_panel.port_port_price_mo_197d":"{port} port <small>{price}/mo</small>",
|
||||
"city_panel.power_cuts_are_covered":"Power cuts are covered.",
|
||||
"city_panel.price_per_gbps_month_billed_on":"${price} per Gbps / month · billed on 95th percentile",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue