Recent disruptions to two undersea internet cables in the Baltic Sea have yet again...
4.17 Exchange
4.17.1 provider.X.rule.Y.bgp_peer #
Defines the BGP Router-ID used for BGP session state monitoring, which is performed by the Internal BGP Monitor (BGP Monitoring).
Depending on whether a Route Server or Peering sessions are used, the parameter value should be set to Route Server Router-ID or Peering Partner Router-ID accordingly.
- Possible values:
IPv4 address
4.17.2 provider.X.rule.Y.enabled #
Defines whether the rule is enabled or not.
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
1
4.17.3 provider.X.rule.Y.next_hop #
Defines the Peering Partner’s IPv4/IPv6 next-hop address.
- Possible values:
IPv4/IPv6 address
4.17.4 provider.X.rule.Y.next_hop_as #
Defines the peering partner’s autonomous system number. This parameter must be set in order for the 3rd algorithm of Bgpd AS-PATH to work properly (refer to bgpd.as_path). If this parameter is set, then it’s value will be used as part of AS-PATH for outgoing improvements if the 3rd algorithm is enabled in bgpd.as_path. In case of Internet Exchanges, the AS-Path begins with peering partner’s AS number, instead of AS number of route server. The first AS number will be stripped from AS-Path when advertising improvement towards Exchange, in case the first AS number is equal to the value set in this parameter.
See also: peer.X.ipv4.next_hop_as, peer.X.ipv6.next_hop_as
- Possible values:
0-4294967295 - Default value:
0
4.17.5 provider.X.rule.Y.pbr_check #
Enables/disables PBR check for a configured peering partner.
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
1
4.17.6 provider.X.rule.Y.probing_dscp #
Defines the DSCP (Differentiated services code point) used with provider.X.rule.Y.probing_ip for a specific Peering Partner.
- Possible values:
0-63
4.17.7 provider.X.rule.Y.probing_ip #
Defines the probing IPv4/IPv6 address used for a specific Peering Partner.
- Possible values:
IPv4/IPv6 address
4.17.8 provider.X.rule.Y.shortname #
Defines a short name for a configured Peering Partner.
- Possible values:
text
4.17.9 provider.X.rule.Y.transit #
The option could be turned on if a Peering Partner provides full Internet access.
IRP will check for route availability, assuming a route is always available.
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
0