SGIX operates 2 route-servers (RS) in Singapore. Once peered with the RS, there is no need to maintain multiple BGP sessions with other members.
Please note the following when peering with RS
- Remove private ASN in the prefix advertisement
- Prefixes stated in RFC 1918 should be removed.
- Disable check on first-ASN. This may be applicable to Huawei (“undo check-first-as”) and Cisco equipment (“no bgp enforce-first-as”)
- RS accepts a maximum of 2,000 prefixes by default.
- Members are advised to peer with both route servers.
- Members can choose to establish or maintain bi-lateral peering arrangement with other members.
- Members agree not to hold SGIX responsible for any impact on traffic flow due to policies request configured at RS by other members.
SGIX route-servers support BGP community attributes. Besides the standard well-known community attributes like NO_EXPORT and NO_ADVERTISE, the following table shows other supported attributes and the top-down evaluation order.
|0:55518||Block announcement of prefixes to all peers|
|0:peer-as||Block announcement of prefixes to peer-as|
|55518:peer-as||Advertise to peer-as only|
Prefixes which are untagged will be advertised to all route server peers. Attributes that do not match SGIX’s attributes will be passed on transparently.
For members having 4-byte ASN, they will be mapped to private ASNs. Hence, prefixes announcement are still possible to be manipulated using community strings.
|Networks||4-byte ASN||Private 2-byte ASN|
|SGIX Public Service Network||132696||65002|
|SimplerCloud Pte Ltd||132816||65003|
|PT BIT Teknologi Nusantara||136838||65004|
|Netpluz Asia Pte Ltd||134078||65006|
|Media Access International||131744||65008|
|Home Box Office (Singapore) Pte Ltd||135278||65009|
|QOXY Pte Ltd||131259||65010|
|Lazada South east Asia Pte Ltd||134171||65011|
|Neuro10 Pte Ltd||134663||65012|
|Atotech SEA Pte Ltd||136451||65013|
|Youzu (Singapore) Pte Ltd||135365||65015|