Technical Info

Route server access for multilateral peering.

PIT Miami route servers help participants exchange routes with multiple networks through a simplified BGP model while keeping bilateral peering available for selected peers.

TopologyDistributed Layer 2 exchange fabric. Interface and CablingSupported optics and handoffs. Traffic GuidelinesAllowed traffic and operational expectations. Route ServerBIRD 2 multilateral peering details.

Route server overview.

PIT Miami route servers run on BIRD 2 and are designed to reduce the operational effort needed to exchange routes with other route server participants on the peering LAN.

Participants can use bilateral sessions, route server sessions or both. The route servers exchange routing information only and do not sit in the forwarding path for participant traffic.

Route server details.

Final production values can be updated here as PIT Miami assigns the definitive ASN and peering LAN addresses.

Route Server	Hostname	ASN	IPv4 Address	IPv6 Address	Platform
RS1	rs1.mia.pit.net	XXXXX	X.X.X.1	XX:XX::1	BIRD 2
RS2	rs2.mia.pit.net	XXXXX	X.X.X.2	XX:XX::2	BIRD 2

Session policy.

Route server sessions should be configured with explicit import and export policy, prefix limits and operational contacts suitable for production peering.

Routing hygiene

Announce only prefixes you are authorized to originate.
Do not announce default routes, private space or bogon prefixes.
Maintain current route and route6 objects where applicable.
Apply max-prefix safeguards aligned with your expected route table.

Operational coordination

Coordinate activation with PIT Miami before bringing sessions into production.
Keep NOC and peering contacts reachable for incident response.
Confirm MD5, BGP role, prefix-limit and filtering requirements during onboarding.
Use bilateral peering where a direct policy relationship is preferred.

Illustrative BGP setup.

This example is intentionally generic. Replace the placeholders with your assigned PIT Miami peering LAN addresses, ASN and production routing policy.

protocol bgp pit_miami_rs1 {
  local as <YOUR_ASN>;
  neighbor X.X.X.1 as XXXXX;
  source address <YOUR_PIT_MIAMI_IPV4>;
  ipv4 {
    import filter <YOUR_IMPORT_POLICY>;
    export filter <YOUR_EXPORT_POLICY>;
  };
}

protocol bgp pit_miami_rs2 {
  local as <YOUR_ASN>;
  neighbor X.X.X.2 as XXXXX;
  source address <YOUR_PIT_MIAMI_IPV4>;
  ipv4 {
    import filter <YOUR_IMPORT_POLICY>;
    export filter <YOUR_EXPORT_POLICY>;
  };
}