AqabaIX route server Informational BGP Communities

Route Origin

The route server will mark all routes with certain BGP Communities to indicate their origin. You can use this information to determine where a certain route has been injected into the AqabaIX switching platform. This gives you the option to filter routes learned from the route servers based on geographical location. 

Currently we tag the following information:

• Switch: Indicates at which switch a prefix has been injected into the AqabaIX platform. We tag the corresponding edge switch of the port.
  • Example: edge01.aqj1
• Metro: The metropolitan region corresponding to the switch
  • Example: Aqaba
• Country: The country corresponding to the above (in M49 format)
  
  • Example:  Jordan
• Continent: The continent corresponding to the above (in M49 format)
  • Example: Asia

This means that every route you will learn from the route servers will have four (additional) BGP Communities (per community class, e.g. each Standard and Large respectively) attached which indicate location information.

To avoid ambiguity about the semantics of a certain BGP Community, especially when being present multiple times, we strip all BGP Communities from the range that we use for route origin tagging on import. This is:

• Standard Community
  
  • 65101:*
  • 65102:*
  • 65103:*
  • 65104:*
• Large Community
  • 207515:1911:*
  • 207515:1912:*
  • 207515:1913:*
  • 207515:1914:*

Overview

Example

A prefix has the following BGP Communities attached to it:

• 65104:142
• 207515:1914:142
• 65103:400
• 207515:1913:400
• 65102:43000
• 207515:1912:38
• 65101:43162
• 207515:1911:162

From these BGP Communities you can deduce that this particular prefix has been injected in Asean (65104:142, 207515:1914:142), Jordan (65103:400, 207515:1913:400) in metro region Aqaba (65102:43000, 207515:1912:38) at edge01.aqj1 (65101:43162, 207515:1911:162).