Route Servers

Route Server	IPv4 Address	Peering AS
ygn_mmix-rs1	103.116.194.1	9654
ygn_mmix-rs2	103.116.194.2	9654

Note: All route servers filter bogon address ranges.

Policy Control with BGP Communities:

MMIX supports BGP Communities to allow participants to manage routing decisions through the route servers. This Provides fine-grained control over outbound route announcemnets.

Supported Communities

Community	Description
0:9654	Block Announcement of Prefixes to all Peers
0:(Peer-as)	Block Announcement of Prefixes to all Peers
9654:(peer-as)	Peer with a specific Member
40027:40000	Advertise to Netflix
9654:20940	Advertise to Akamai
9654:54994	Advertise to Wangsu
9654:11344	Advertise to GGC

Example Configurations

Basic BGP Session Setup with MMIX Route Servers

    
      router bgp {Your_ASN}

      no bgp enforce-first-as

      neighbor 103.116.194.1 remote-as 9654

      neighbor 103.116.194.2 remote-as 9654

Note:no bgp enforce-first-as command is necessary to avoid AS path validation issues when connecting with MMIX route servers.

Subscribe to CDN Services

To configure the subscription for CDN services, enable the sending of communities and apply a route map for outbound announcements.

    
      router bgp {Your_ASN}

      no bgp enforce-first-as

      neighbor 103.116.194.1 remote-as 9654

      neighbor 103.116.194.2 remote-as 9654

      neighbor 103.116.194.1 send-community

      neighbor 103.116.194.2 send-community

      neighbor 103.116.194.1 route-map RM-MMIX-OUT out

      neighbor 103.116.194.2 route-map RM-MMIX-OUT out

      //Configure the route map to set the necessary communities://

      route-map RM-MMIX-OUT permit 10

      set community 9654:20940 9654:54994 9654:11344 40027:40000

Block Peer with Single Member:

Example to block announcement to per peer(e.g., Seanet Myanmar):


      router bgp {Your_ASN}

      no bgp enforce-first-as

      neighbor 103.116.194.1 remote-as 9654

      neighbor 103.116.194.2 remote-as 9654

      neighbor 103.116.194.1 send-community

      neighbor 103.116.194.2 send-community

      neighbor 103.116.194.1 route-map RM-MMIX-OUT out

      neighbor 103.116.194.2 route-map RM-MMIX-OUT out


      //In the route-map, set the community to block the peer//

       //*you can chek members' 2byte ASN info here *//

      route-map RM-MMIX-OUT permit 10

      set community 0:65002

Peer with Single MMIX Members:

To configure peering with a specific MMIX member, apply the following configuration:

    
      router bgp {Your_ASN}

      no bgp enforce-first-as

      neighbor 103.116.194.1 remote-as 9654

      neighbor 103.116.194.2 remote-as 9654

      neighbor 103.116.194.1 send-community

      neighbor 103.116.194.2 send-community

      neighbor 103.116.194.1 route-map RM-MMIX-OUT out

      neighbor 103.116.194.2 route-map RM-MMIX-OUT out

      //For the route map, set the community to peer with the specific member://

      route-map RM-MMIX-OUT permit 10

      set community 9654:65002 0:9654

Note: 0:9654 is used to block peering with all MMIX peers.

Conclusion

MMIX provides route servers at each Peering LAN, enabling participants to establish multilateral peering efficiently. With the support of BGP communities, members can exercise granular control over outbound announcements, including blocking specific peers, peering with individual members, and subscribing to CDN services. Proper configuration of BGP sessions, community attributes, and route maps ensures seamless integration with MMIX's routing policies while optimizing network performance and connectivity.