Overview
When you peer with us, you need to create (or update) and maintain, at a minimum, your maintainer, autonomous system and route objects for Google to accept your BGP advertisements. In some cases you might also need an AS-SET object. Update the AS-SET object at your PeeringDB record.
Case 1: Consumer Focus ISP
In this example all the IP space announced by the ISP originates from its own ASN, the prefix 192.0.2.0/24 / AS64496. The transit provider of AS64496 is AS65551. The AS and route objects would look like this:
AS Object
aut-num: AS64496
as-name: My_ISP
descr: My ISP Inc.
import: from AS-65551 accept ANY
export: to AS-ANY announce AS64496 AND NOT {0.0.0.0/0}
admin-c: My ISP Contact
tech-c: My ISP Contact
notify: noc@example.com
mnt-by: MAINT-AS64496
Route Object
route: 192.0.2.0/24
descr: My_ISP
Descr: Somewhere, Some Country
origin: AS64496
mnt-by: MAINT-AS64496
Case 2: Transit ISP
In this example the ISP AS65551 provides transit services to other ASNs. AS65551 originates 198.51.100.0/24 and AS64496 (the customer) originates 192.0.2.0/24. Both ASNs need objects to have been created for Google to accept BGP advertisements from peering with AS65551. The transit provider, AS65551, needs to create an AS-SET as shown below that contains all the ASNs to which it provides connectivity. Configure the AS-SET ("AS-TRANSITISP" in this example) in the “IRR Record” field of your PeeringDB.com record for Google to process the AS-SET.
Customer
AS Object
aut-num: AS64496
as-name: My_ISP
descr: My ISP Inc.
import: from AS-65551 accept ANY
export: to AS-ANY announce AS64496 AND NOT {0.0.0.0/0}
admin-c: My ISP Contact
tech-c: My ISP Contact
notify: noc@example.com
mnt-by: MAINT-AS64496
Route Object
route: 192.0.2.0/24
descr: My_ISP
Descr: Somewhere, Some Country
origin: AS64496
mnt-by: MAINT-AS64496
Transit Provider
AS Object
aut-num: AS65551
as-name: Transit_ISP
descr: My Transit Inc.
import: from AS-ANY accept ANY
export: to AS-ANY announce AS-TRANSITISP
admin-c: Transit ISP Contact
tech-c: Transit ISP Contact
notify: transit@example.com
mnt-by: MAINT-AS65551
AS-SET object (Add this to your PeeringDB record)
as-set: AS-TRANSITISP
descr: Transit ISP AS Set
members: AS65551
members: AS64496
Route Object
route: 198.51.100.0/24
descr: Transit_ISP
Descr: Somewhere, Some Country
origin: AS65551
mnt-by: MAINT-AS65551
The AS-ASET ("AS-TRANSITISP" in this case) has to be configured on the “IRR Record” field of your PeeringDB record.