Establish multilateral peering with other participants through MMIX route servers
MMIX maintains route servers at each of the Peering LANs allowing members to establish multilateral peering with other participants.
| Route Server | IPv4 Address | Peering AS |
|---|---|---|
| ygn_mmix-rs1 | 103.116.194.1 | 9654 |
| ygn_mmix-rs2 | 103.116.194.2 | 9654 |
| mdy_mmix-rs1 | 103.116.193.1 | 9333 |
| mdy_mmix-rs2 | 103.116.193.2 | 9333 |
Please use the correct AS number and IP addresses based on your peering location:
When configuring peering:
Example configuration for establishing basic BGP sessions 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
The no bgp enforce-first-as command is necessary to avoid AS path validation issues when connecting with MMIX route servers.
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
route-map RM-MMIX-OUT permit 1000
Ensure send-community is configured to activate community configuration.
Example to block announcement to a specific 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:
route-map RM-MMIX-OUT permit 10
set extcommunity rt 0:132344
route-map RM-MMIX-OUT permit 1000
Since we are using 4byte ASN, we have to use Extended Community. Click Me to see all supported communities.
Ensure send-community is configured to activate community configuration.
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 extcommunity rt 9654:132344
route-map RM-MMIX-OUT permit 20
set extcommunity rt 0:9654
rt 0:9654 is used to block peering with all MMIX peers. However, we support bilateral BGP peering with specific members upon request.
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.
Our technical team is ready to assist you with implementing these configurations.
Contact Technical Support