I. Communities
Integra allows customers to manipulate their network announcements by sending BGP communities. Customers can send communities to adjust Integra local preference, and modify export behavior. Customers can use various combinations of these communities to control their inbound traffic flows.
Integra strips any unrecognized BGP communities received from the customer. Integra does not propagate any BGP communities to non-customers, originated by Integra or otherwise.
Local Preference Manipulation
Integras Backbone Local Preference Policy uses the following values:
| 65, 75, 80, 85 | Integra Peers |
| 100 | Integra BGP Customers (default) |
| 100 | Integra Internal and static routed customers |
Customers may send the following communities to modify BGP local preference given to networks announced to Integra:
| Community | Integra Local Preference | Effect on Integra Route Preference |
| 7385:60 | 60 | Last Resort -- Only use this route when alternate providers no longer have this route. |
| 7385:70 | 70 | Backup #2 -- Allows the customer to specify that the circuit on which ths route is learned is to be a backup to another circuit with Integra (since default is set to 100). Also causes the same route to be preferred if learned from and Integra Bilateral peer over the route marked with this community. |
| 7385:90 | 90 | Backup #1 -- Allows the customer to specify that the circuit on which this route is learned is to be a backup to another circuit with Integra |
| 7385:110 | 110 | Preferred -- This route is preferred over all others |
Customers may send the following communities to modify Integra default export behavior, which is to export all accepted routes (assuming they have passed Integra filters) to all BGP peers including customers:
| Community | Export Behavior |
| 7385:640 | Do not export to any BGP peers or customers (similar to well known community 'no-export') |
| 7385:666 | Do not export to any BGP peers, but do export to Integra BGP customers |