In recent years, the concepts of Artificial Intelligence (AI) and Machine Learning (ML)...
4.16 Routing Policy
IRP used a legacy format for policies.conf where a single policy parameters immediately followed the prefix/ASN that defined them. IRP updated policies.conf format and assigned each policy a unique identifier of the form “policy.X.” used to prefix each attribute. Notice the format changes in the samples below.Legacy routing policy example:
asn=65530
vip=0
policy=deny
providers=1 3 5
enabled=1
notes=AS65530 deny via Level3, Cogent and nLayer
Normalized routing policy example:
policy.1.asn=65530
policy.1.vip=0
policy.1.policy=deny
policy.1.providers=1 3 5
policy.1.enabled=1
policy.1.notes=AS65530 deny via Level3, Cogent and nLayer
4.16.1 policy.X.asn #
Defines the Autonomous System Number which is used to match prefixes from the BGP routing table, originated from the specified ASN.
Only one matching parameter should be specified per policy- Possible values:
1-4294967295
4.16.2 policy.X.cascade #
Defines the ASN policies that cascade to downstream AS from designated AS. The parameter applies to ASN policies (and not to prefixes).
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
0
4.16.3 policy.X.community #
A community to mark improvements belonging to a policy.
- Possible values:
X:Y
4.16.4 policy.X.country #
Defines the two-character country code which is used to match prefixes from the internal geodata database.
Only one matching parameter should be specified per policy- Possible values:
Two-character ISO country Code
4.16.5 policy.X.enabled #
Defines whether the policy is enabled or not
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
1
4.16.6 policy.X.forcelocal #
If the parameter is enabled then global improvements aren’t performed.
Refer: policy.X.policy
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
0
4.16.7 policy.X.notes #
Defines a description of the routing policy
- Possible values:
text
4.16.8 policy.X.policy #
Defines the type of policy.
- allow IRP ensures that traffic flows only via providers listed in the policy.X.providers parameter
deny IRP ensures that traffic does not flow via providers listed in policy.X.providers parameter
static IRP selects prefixes matched by a corresponding parameter from the BGP routing table and makes static improvements via provider(s) specified in the policy.X.providers parameter.
static_exact This option can be enabled when the policy.X.preffix parameter gets used.
- Possible values:
allow, deny, static, static_exact - Default value:
allow
4.16.9 policy.X.prefix #
Defines the aggregate prefix which is used to match sub-prefixes from the BGP routing table.
If the policy.X.policy parameter is set to “static_exact” then the prefix is used “as-is” to make a route via specified provider(s).
If the policy.X.policy parameter is set to “static” or “static_exact” and the policy.X.forcelocal parameter is enabled, then multiple providers (one per routing domain) can be specified in the policy.X.providers parameter.
Refer: policy.X.forcelocal, policy.X.policy
Only one matching parameter should be specified per policy- Possible values:
Valid IPv4 or IPv6 prefix
4.16.10 policy.X.priority #
Defines what policy to prioritize in case of overlapping prefixes as might be the case of a large aggregate prefix policy extending over an ASN policy. The same specific prefixes might be covered by both and priority sets which one to actually enforce in favor of the others. Policies with higher priority are prioritized.
- Possible values:
0-1000 - Default value:
0
4.16.11 policy.X.providers #
Defines the list of providers (IDs) affected by the policy. If the ‘providers’ property is not specified, then all the providers will be included in the policy by default.
- Possible values:
1-unlimited
4.16.12 policy.X.vip #
Defines whether VIP probing is enabled for the specified policy.
- Possible values:
0 (Disabled), 1 (Enabled) - Default value:
0