How To Pull Up

Wanna connect to SFMIX? Say less, here's how.

Overview

Peep the pricing and requirements below
Email tech-c@sfmix.org with your desired speed and location; we’ll confirm port availability
Tip: Use subject “New Connection Request – [Your Org Name]” and include your PeeringDB URL, desired speed, and preferred location. We usually hit you back within 1–2 business days.
Fill out the Membership Application
SFMIX issues an LOA/CFA for you to order a cross-connect with the datacenter operator
SFMIX hooks you up with your IPv4 and IPv6 addresses
Your circuit gets connected to a Quarantine VLAN — a safe environment to bring up your link and validate config before touching production (lowkey clutch)
Once you’re ready, SFMIX moves your port to the production peering VLAN
Start peering! Bet.

Administrative Requirements

Pricing

Yearly membership fees, no cap (as of 2023):

Port Speed	Yearly Bag	The Tea
1 Gbps	$995/year	10G with a rate limit > stacking multiple 1G ports, no debate
10 Gbps	$2,995/year	Up to 4 ports in a LAG
100 Gbps	$7,495/year	No LAG limit (go off)

Fee exemptions get judged case-by-case for non-profits putting in in-kind services that benefit every member of the exchange equally (e.g., root DNS, ccTLD/gTLD, public measurement tools) — real green flag energy. Hit up tech-c@sfmix.org to drop an appeal for a fee exemption.

Billing

Annual billing (calendar year); no monthly option
USD only
Payment (preferred order): ACH, wire, check, credit card

Logistical Requirements

At least one rep has gotta subscribe to the sfmix-members mailing list. Role accounts encouraged. Email tech-c@sfmix.org to subscribe.
Mailing list discussions stay confidential to participants, members, and sponsors. Don’t be a snitch.
SFMIX is volunteer-run. All services are best-effort; no SLA is implied. We do what we can fr.
Participants may peer at a single location only, regardless of port count. SFMIX is a peering fabric, not a transport network. Stay in your lane.
No ARP/ICMPv6 spoofing or traffic sniffing. That’s a red flag, don’t do it.

Technical Requirements

SMF only — no copper or MMF. We don’t do that here.
A public RIR-assigned ASN is required (RFC 1930, RFC 6996). No private ASNs.
A maintained PeeringDB entry is required. Keep it fresh.
One MAC address per logical link. Port security allows 2 MACs temporarily for router migrations, but only 1 long-term.
Allowed broadcast: ARP and ICMPv6 ND only. No RAs, CDP, DHCP, or STP.
LLDP: SFMIX transmits LLDP on all participant ports, including optical receive power levels. Participants may transmit LLDP but aren’t required to.
BGP session with the Looking Glass is mandatory. It’s used only for debugging — no routes are redistributed, no traffic exchanged. Non-negotiable, no cap.
Do not propagate SFMIX peering subnets (206.197.187.0/24, 2001:504:30::/64) beyond your edge router. Use ACLs if needed.
No static or default routes toward other participants or SFMIX resources without permission. Ask first.
Route server peering is encouraged but not required.

LLDP & Optical Power Monitoring

SFMIX switches transmit LLDP on every participant port. On top of standard LLDP info (system name, port description), each frame includes the optical receive power measured by the SFMIX-side transceiver, encoded as an LLDP-MED Inventory TLV.

This lets you see — straight from your own router — how well your transmit light is landing at the SFMIX switch, without needing to ping us for support. Self-service W.

What’s advertised

The LLDP-MED Asset ID field carries the receive power in dBm:

Single-lane optics example: dBm:-2.05
Multi-lane optics example: dBm:-7.60/-8.20/-6.79/-6.52 (one value per lane)

Viewing the data

On Arista EOS:

switch# show lldp neighbors Ethernet1 detail | grep 'Asset ID'
  - LLDP-MED Inventory Asset ID TLV: "dBm:-2.05"

On Linux (lldpd):

$ lldpcli show neighbors
  LLDP-MED:
    Inventory:
      Asset ID:     dBm:-2.05

On Juniper Junos:

user@router> show lldp neighbors interface xe-0/0/0

On other platforms, look for LLDP-MED Inventory or organizationally-defined TLVs with OUI 00:12:BB, subtype 11.

Interpreting the values

The power values represent what the SFMIX transceiver is receiving from your side. If you see values dropping toward the transceiver’s receiver sensitivity threshold (typically around −14 dBm for LR4, −22 dBm for ER4), your fiber plant might need some attention. A value of dBm:-40.00 or the absence of an Asset ID TLV means no light is detected — that’s an L, check your stuff.

Optical power via LLDP is currently supported on Arista edge ports only, which covers basically all peering ports today. The agent that injects this data is open source: LldpDomAgent on GitHub.