4.15 Inbound rule

4.15.1 inbound.rule.X.bgp_peer #

Defines the router(s) where IRP announces improvements of this inbound prefix.

Possible values: a router identifier(s) separated by space

4.15.2 inbound.rule.X.communities #

The list of additional BGP communities that will be set for the Inbound Prefix.

4.15.3 inbound.rule.X.enabled #

Enables or disables Inbound Optimization for this prefix.

Possible values: 0 (Disabled), 1(Enabled)
Default value: 1

4.15.4 inbound.rule.X.full_control #

Specifies individual inbound prefix control level by IRP. Default behavior can be set at system level under bgpd.full_control. The settings specify whether default behavior is inherited from the system level or set individually for this prefix to announce either Improvements only or fully announce the prefix to allowed providers.

Possible values: -1 (Use default), 0 (Improvements), 1 (If improved), 2 (All)
Default value: -1

4.15.5 inbound.rule.X.next_hop #

Defines a next_hop specific for the inbound rule. When the next_hop is unset, then a value from bgpd.peer.X.inbound.ipv4.next_hop/bgpd.peer.X.inbound.ipv6.next_hop is taken.

Next-hop should point to a router that routes/terminates traffic. Otherwise null route should be configured for the Next-Hop.

next_hop value should be of the same IP address family as the inbound prefix it is assigned to. Refer inbound.rule.X.prefix.

Possible values: IP address

4.15.6 inbound.rule.X.prefix #

Defines an inbound prefix. Inbound prefixes should belong to your network.

Inbound Optimization of transit networks will be supported in future releases.

Each inbound prefix logically extends the list of ournets when it is processed by IRP Collector. Refer collector.ournets.

Possible values: prefix in CIDR format

4.15.7 inbound.rule.X.providers #

Defines the list of providers where this inbound prefix can be advertised. In case this parameter value is empty then it is treated as prefix will be advertised to ALL providers.