Single vs.
Multi-homed Options
- Single-homed: Can use static routes pointed to
the customer’s equipment.
- Multi-homed: Must use BGP. Customer connects to
multiple CCI PE routers.
- Can use a private ASN or one assigned by ARIN.
- Multi-homed: Must use BGP. Customer connects to
CCI and a different service provider.
- Must use an ARIN assigned ASN. The ASN needs to
be verifiable in WHOIS.
Accepted Route Prefixes
All customer route announcements must be
registered with a regional registrar such as the ARIN RR or RADb.
- The advertised route must be equal to or fall
within a valid route-object when performing a RADb query.
- For example: If the customer sends us two /24
routes, we do not need two specific /24 route-objects if they can and do roll
up into a single /23 route-object.
- RADb query:
http://www.radb.net/query/
- The route-object’s “origin” must match the ASN
that the routes will originate from in BGP.
- The origin AS is the right-most ASN in the
as-path of the BGP route.
CCI will announce any prefix so long as they
meet the following:
- The prefix is equal to or larger than a /24 (a
larger prefix means a smaller prefix length number).
- For example: A /23 prefix is larger than a /24
prefix.
- The prefix falls within a net block that is
assigned to the customer via WHOIS or RWHOIS databases.
- The prefix has a matching route-object (for
falls within one) in a regional registrar.
- We have received a valid LOA (Letter of Agreement)
from the owner of the block.
- We do not need an LOA for each and every prefix
the customer advertises to us, as long as they fall within a block that is
specified in the LOA.
Customers should apply an outbound BGP filter to
prevent unintended routes from being announced to CCI.
- CCI may disable the BGP peering automatically if
the number of prefixes advertised by the customer is larger than the requested
number.
Customer Equipment Requirements
- Customers must use a router that supports BGPv4
&/or BGPv6.
- Customers are responsible to ensure their
peering routers have adequate CPE processing power and memory space if a full
Internet table is requested.
- CCI will employ all best-known practices to
establish, maintain, and troubleshoot BGP sessions with all BGP compliant router
vendors. However, CCI makes no warranty that it can establish and maintain a
BGP session with any CPE due to vendor interoperability.
Customers
can specify one of the following received-prefixes options:
- Default-route only
- CCI customer routes/Partial routes
- Full routes
CCI
<-> Customer Interconnect Subnet for Peering
- BGPv4 (IPv4)/BGPv6(IPv6): CCI will assign an IP
address for the customer’s router interface that connect to CCI’s network along
with an IP address that the customer can use to establish a BGP Peer with CCI. This will be assigned from a CCI address
block publicly registered with ARIN and already advertised as part of a larger
aggregate to the Internet.
Miscellaneous
requirements/notes:
- The customer must be connected on a link with
2Mbps or higher bandwidth to establish BGP with CCI.
- Customer must be capable of configuring their
BGP session with CCI. This includes all setup of neighbor statements and all
sanity checks on customer CPE.
- CCI will recommend to the customer the use of an
MD5 authentication key for the BGP session. If the customer agrees to use MD5
authentication then they should supply the password.
- CCI has the right to disable any BGP peer in the
event of any network anomaly caused the BGP peering.