Customer BGP Policy
Receivable Communities
Customers may influence WV Fiber routing policies by a number of community tags which may be set on routes which they announce. These tags can control the propagation of routes, adjust the localpref assigned to them, and even null route traffic. Improper community use can cause prefix rejection.
| Receivable Communities |
| Community |
Action |
| 19151:666 |
Blackhole. Sets null route across network. |
| 19151:295 |
Reduced localpref (-5) |
| 19151:305 |
Reduced localpref (-3) |
| no-export |
Well known attribute. |
| no-advertise |
Well known attribute. |
Announced Communities
All routes announced to customers are tagged with the following information:
19151:community
Communities are set regionally, by hub, and by type. Other communities may be present that are special purpose or passed on.
| East Coast US 19151:1000 |
| City |
Community |
| Ashburn |
19151:61001 |
| New York |
19151:61003 |
| Pittsburgh |
19151:61005 |
| Atlanta |
19151:61006 |
| Miami |
19151:61007 |
| Columbus |
19151:61008 |
| Central US 19151:2000 |
| City |
Community |
| Nashville |
19151:62001 |
| Dallas |
19151:62002 |
| Madison |
19151:62003 |
| Chicago |
19151:62006 |
| Indianapolis |
19151:62008 |
| Western US 19151:3000 |
| City |
Community |
| Seattle |
19151:63001 |
| San Jose |
19151:63002 |
| Los Angeles |
19151:63005 |
| Las Vegas |
19151:63007 |
| Europe 19151:4000 |
| City |
Community |
| London |
19151:64001 |
| Amsterdam |
19151:64002 |
| Local Preferences |
| Localpref |
Description |
| 100 |
Default transit route |
| 200 |
Default peering route |
| 300 |
Default customer route |
| 400 |
Default internal route |
IRR Filtering
All customers announcements are filtered against Internet Routing Registry (IRR) databases. BGP speaking customers will be expected to maintain current and correct IRR entries.
All WV Fiber announcements will be recorded under the as-set AS-WVFIBER.