![]()
Routing Info
| Community | Local-pref | Description |
|---|---|---|
| Verio BGP customers may choose to affect our local preference on their routes by marking their routes with the following communities: | ||
| (default) | 120 | customer |
| 2914:490 | 120 | customer default |
| 2914:480 | 110 | customer backup |
| 2914:470 | 100 | peer |
| 2914:460 | 98 | peer backup |
| 2914:450 | 96 | customer fallback |
| Verio BGP customers may choose to prepend to all Verio peers with the following communities: | ||
| 2914:429 | do not advertise to any peer | |
| 2914:423 | prepends o/b to peer 3x | |
| 2914:422 | prepends o/b to peer 2x | |
| 2914:421 | prepends o/b to peer 1x | |
| Verio BGP customers may choose to prepend to all other Verio BGP customers with the following communities: | ||
| 2914:413 | prepends o/b to customer 3x | |
| 2914:412 | prepends o/b to customer 2x | |
| 2914:411 | prepends o/b to customer 1x | |
| Verio BGP customers may choose to prepend to selected tier 1 peers with the following communities, where nnn is the tier 1 peer's ASN. | ||
| 65500:nnn | do not announce to tier 1 peer | |
| 65501:nnn | prepend o/b to tier 1 peer 1x | |
| 65502:nnn | prepend o/b to tier 1 peer 2x | |
| 65503:nnn | prepend o/b to tier 1 peer 3x | |
Note:2914 is the ASN prepended in all cases.
Verio sends routes to customers marked with the following communities.
| Community | Interpretation |
|---|---|
| 2914:410 | Verio and customer routes |
| 2914:420 | Peer routes |
| 2914:20-- | North American country origins |
| 2914:2000 | US |
| 2914:22-- | European country origins |
| 2914:2201 | uk |
| 2914:2202 | de |
| 2914:2203 | nl |
| 2914:2204 | fr |
| 2914:2205 | es (Spain) |
| 2914:24-- | Asian country origins |
| 2914:2401 | jp |
| 2914:2402 | au |
| 2914:2403 | hk |
| 2914:2404 | tw |
| 2914:2405 | kr |
| 2914:2406 | sg |
| 2914:2407 | my |
| 2914:3--- | world region origins |
| 2914:3000 | North America |
| 2914:3200 | Europe |
| 2914:3400 | Asia |
BGP IPv4 peer filter policy The following is Verio's filtering policy with its peers:
inbound:
outbound:
Verio reserves the right to modify this policy without prior notice.
inbound:
outbound:
Verio reserves the right to modify this policy without prior notice.
Route dampening is a BGP feature designed to minimize the propagation of flapping routes across an internetwork. A route is considered to be flapping when it is repeatedly available, then unavailable, then available, then unavailable, and so on.
The Route Dampening Process:
The route dampening feature minimizes the flapping problem as follows.
Suppose a route in network A flaps. A route that is flapping receives a penalty of 1000 for each flap and moves it to "history" state. When the route flaps so often that the penalty exceeds a configurable suppress limit, the router stops advertising the route, regardless of how many times it flaps. Thus, the route is dampened.
The accumulated penalty is decremented by the half-life time. When the accumulated penalty is less than the reuse limit, the dampening information for the route is removed and the route is advertised again.
Verio sets different dampening parameters for different sizes of address blocks across the network.
a) For /24 and longer prefixes: max=min outage 60 minutes half-life = 30 Maximum suppress limit = 60 Reuse limit = 820 Suppress limit = 3000
b) for /22 and /23 prefixes: max outage 45 minutes but potential for less because of shorter half life value - minimum of 30 minutes outage Half-life = 15 Maximum suppress limit = 45 Reuse limit = 750 Suppress limit = 3000
c) all else prefixes: max outage 30 minutes min outage 10 minutes Half-life = 10 Maximum suppress limit = 30 Reuse limit = 1500 Suppress limit = 3000
Understanding Route Dampening Terms:
The following terms are used when describing route dampening:
The routes external to an AS learned via IBGP are not dampened. This policy prevent the IBGP peers from having a higher penalty for routes external to the AS.