Some network services require you to set up a session with a route server. Route Servers are considered network features and you will have to create a network feature config for each feature marked as required.
Network features are additional functionalities to network services. Currently, there is only a single type of network features, which is route_server. Those route server network features only make sense in the context of peering (i.e. Public Peering or MAPS).
You can find all existing network features with the
network_features_list
operation.
Network features have flags which represent configuration
options. For example, an exchange may choose to enable the client
to configure RPKI filtering on the BGP session. In this case, the
network feature returns a flag called RPKI with an appropriate
description. Some of those flags are always enabled. As such,
their mandatory property is set to true which means they may
never be disabled. The purpose of those mandatory flags is
purely for documentation.
[
{
"type": "route_server",
"id": "string",
"name": "string",
"required": true,
"nfc_required_contact_roles": [
"role:noc", "role:implementation"
],
"flags": [
{
"name": "RPKI-HARD-FILTER",
"description": "RPKI reject invalid filtering is available",
"mandatory": true
}
],
"network_service": "string",
"asn": 0,
"fqdn": "rs1.example.ix",
"looking_glass_url": "https://lg.example.ix/rs1",
"address_families": [
"af_inet"
],
"session_mode": "public",
"available_bgp_session_types": [
"passive"
],
"ip_v4": "192.42.23.1",
"ip_v6": "2001:23:42::1"
}
]
Network features describe route server instances while network
feature configs describe sessions on those instances. In order to
create a route-server session, you would first need to have a
fully provisioned network service config which means it is in
state production (or in an error state if the NFC is required for
that NSC). It is safe to assume that this network service config
contains ip addresses that can be used in the peering context and
that corresponding network service refers to a list of network
features. You can create the NFC with
network_feature_configs_create.
There can be one BGP session between each pair of NSC IP addresses and network features. You have to choose the IP address from the list of IPs of the NSC and specify it as part of the NFC creation.
{
"type": "route_server",
"managing_account": "<my_account_id>",
"billing_account": "<my_account_id>",
"consuming_account": "<customer_account_id>",
"role_assignments": [
"c-impl:123",
"c-noc:331"
],
"network_feature": "<ns_id>",
"network_service_config": "<nsc_id>",
"flags": [
{
"name": "RPKI-HARD-FILTER",
"enabled": true
}
],
"asn": 4200000023,
"password": "bgp-session-test-23",
"as_set_v4": "MOON-AS@RIPE",
"as_set_v6": "MOON-AS@RIPE",
"max_prefix_v4": 5000,
"max_prefix_v6": 5000,
"insert_ixp_asn": true,
"session_mode": "public",
"bgp_session_type": "passive",
"ip": "<ip_address_id>"
}