Skip to main content

Documentation Index

Fetch the complete documentation index at: https://deribit-starbase.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Quick Start Guide

The IP address 224.0.12.234 used in the examples below is illustrative only. Replace it with the actual multicast group address for your feed. See the full list of available feeds on the Multicast Channels page.

For Colo Customers (Direct Connection)

Best for customers connected via active/backup bond interfaces.
  1. Identify your interface: Usually bond0.
  2. Subscribe: Run the join command on your server:
    smcroutectl join bond0 <mcast-address>
    
  3. Verify: Check your local interface for incoming traffic.
  4. Unsubscribe: Run the leave command:
    smcroutectl leave bond0 <mcast-address>
    

For Cross-Connect Customers (BGP/PIM)

Best for customers using routing devices with BGP peering.
  1. Configure PIM RP: Set the Rendezvous Point on your routing device:
    RP ADDRESS: 195.138.37.160
    
  2. Enable PIM: Ensure ip pim sparse-mode is active on all interfaces facing the Starbase Gateway.
  3. Subscribe: Send an IGMPv3 membership report from your server:
    smcroutectl join [interface] <mcast-address>
    
  4. Verify: Check the PIM neighbor status and mroute table on your switch.

Configuration Reference

Verification Commands

To confirm the ASM tree is building correctly toward the RP:
CommandPurpose
show ip pim neighborCheck neighbors (ensure status is “sparse”)
show ip pim rpCheck RP (should point to 195.138.37.160)
show ip mrouteCheck routing (verify outgoing interface is correct)
show ip pim rp-hash <mcast-address>Confirm RP mapping (should return 195.138.37.160)
show ip mroute <mcast-address>Check shared tree (*, G) entry pointing toward the RP